Rendering visual components on applications in response to voice commands

ABSTRACT

The present disclosure is generally related to systems and methods of rendering visual components on applications. At least one action-inventory can indicate to render a user interface component. A data processing system can identify a request from an input audio signal from a client device. The client device can display a first application in a foreground process. The data processing system can select an action-inventory to execute the action corresponding to the request by a second application. The data processing system can generate an action data structure using the action-inventory to provide to the second application. The data processing system can determine that an output of the second application is authorized to be presented with the first application. The data processing system can display, on the client device, a user interface component from the second application with the first application.

BACKGROUND

Applications can be installed on a computing device. The computingdevice can execute the application. The application can present digitalcontent.

SUMMARY

According to a first aspect of the disclosure, a system to render visualcomponents on applications. The system can include an agent registryexecuted on a data processing system having one or more processors. Theagent registry can maintain a plurality of action-inventories for aplurality of applications. At least one of the plurality ofaction-inventories can indicate to render a user interface component forone of the plurality of applications in executing an action. The systemcan include a natural language processor executed on the data processingsystem. The natural language processor can receive a data packetcomprising an input audio signal detected by a sensor of a clientdevice. The client device can display a graphical user interface of afirst application in a foreground process on the client device. Thenatural language processor can parse the input audio signal of the datapacket to identify a request. The system can include an action handlerexecuted on the data processing system. The action handler can select,from the plurality of action-inventories, an action-inventory thatexecutes the action corresponding to the request by a second applicationof the plurality of applications. The second application can beinstalled on the client device and not in the foreground process. Theaction handler can generate an action data structure in accordance withthe action-inventory. The system can include an agent interface executedon the data processing system. The agent interface can provide theaction data structure to the second application to cause the secondapplication to parse the action data structure and execute the action togenerate an output. The agent interface can determine that the output ofthe second application from execution of the action is authorized to bepresented with the graphical user interface of the first applicationbased on an authorization policy of the second application. The agentinterface can identify the user interface component of the secondapplication for the action-inventory selected from the plurality ofaction-inventories, responsive to the determination the output of thesecond application is authorized to be presented with the firstapplication. The agent interface can display, on the client device, theuser interface component including the output from the secondapplication with the graphical user interface of the first applicationauthorized to be presented with the second application.

At least one of the plurality of action-inventories may have an addresstemplate for accessing the user interface component in executing theaction, the address template defining a first portion and a secondportion, the first portion corresponding to one of the plurality ofapplications, the second portion including an input variable in carryingout the action. The natural language processor may parse the input audiosignal of the data packet to identify a parameter defining the requestto be executed by the second application. The action handler maygenerate, in accordance with the address template of theaction-inventory, an address to execute the action of theaction-inventory, the address comprising a first substring and a secondsubstring, the first substring corresponding to the second application,the second substring having the parameter used to control execution ofthe action; and generate the action data structure including the addressgenerated by the action handler in accordance with the address template.

At least one of the plurality of action-inventories may have an addresstemplate for accessing the user interface component in executing theaction, the address template defining a first portion and a secondportion, the first portion corresponding to one of the plurality ofapplications, the second portion including an input variable in carryingout the action. The natural language processor may parse the input audiosignal of the data packet to identify the parameter defining the requestto be executed by the second application. The action handler togenerate, in accordance with the address template of theaction-inventory, an address to execute the action of theaction-inventory, the address comprising a first substring and a secondsubstring, the first substring corresponding to the second application,the second substring having the parameter used to control execution ofthe action. The agent interface may identify the user interfacecomponent of the second application for the action-inventory selectedfrom the plurality of action-inventories using the address generated inaccordance with the address template for the action-inventory.

Each action-inventory may have an agent identifier corresponding to oneof the plurality of applications and a request identifier correspondingto the action. The natural language processor may parse the input audiosignal of the data packet to identify an agent identifier correspondingto an agent , the agent corresponding to the second applicationinstalled on the client device. The action handler may select, from theplurality of action-inventories, the action-inventory for executing theaction having the agent identifier corresponding to the agent identifieridentified from parsing the input audio signal.

The action handler may determine that the interface mode indicator ofthe action-inventory specifies rendering of the user interface componentin executing the action, and identify the user interface component ofthe second application for the action-inventory, responsive to thedetermination that the interface mode indicator specifies rendering ofthe user interface component.

The agent interface may determine that the client device is notauthenticated with the second application for the action-inventory tocarry out the action corresponding to a second request; and may present,responsive to the determination that the client device is notauthenticated with the second application, a prompt interface on theclient device to authenticate the client device with the secondapplication to execute the action corresponding to the second request.

The agent interface may determine that an output of a third applicationis not authorized to be presented with the first application based on anauthorization policy of the third application, the third applicationinstalled on the client device and not in the foreground process, setthe third application as the foreground process of the client device,the first application transferred from the foreground process to anon-foreground process running on the client device, and display, on theclient device, a graphical user interface of the third applicationincluding an output generated by the third application.

The agent interface may determine that the first application authorizespresentation of the user interface component of the second applicationwith the graphical user interface of the first application based on anauthorization policy of the first application, the authorization policypermitting user interface components from a first subset of theplurality of applications to be presented with the graphical userinterface and restricting user interface components from a second subsetof the plurality of applications to be presented with the graphical userinterface, and display, on the client device, the user interfacecomponent including the output from the second application with thegraphical user interface of the first application, responsive to thedetermination that the first application authorizes the presentation ofthe user interface component of the second application with thegraphical user interface of the first application.

The agent interface may provide the action data structure to the secondapplication to cause the second application to monitor for aninteraction event on the user interface component from the secondapplication presented with the graphical user interface of the firstapplication and process, responsive to detection of the interactionevent, the interaction event to update the user interface component.

The natural language processor may receive the data packet via a digitalassistant application, the data packet comprising the input audio signaldetected by the sensor of the client device, the client devicedisplaying the graphical user interface of the digital assistantapplication corresponding to the first application in the foregroundprocess. The agent interface may display, within the graphical userinterface of the digital assistant application, the user interfacecomponent including a subcomponent indicating the request identifiedfrom parsing the input audio signal and the user interface componentincluding the output from an agent corresponding to the secondapplication. The agent may lack natural language processingcapabilities.

The natural language processor may receive the data packet, the datapacket comprising the input audio signal detected by the sensor of theclient device, the client device displaying the graphical user interfaceof a first agent corresponding to the first application in theforeground process; and the agent interface to display the userinterface component including the output from the second application asan overlay on the graphical user interface of the first agent.

The plurality of action-inventories may have a first subset ofaction-inventories and a second subset of action-inventories, the firstsubset including action-inventories defined by an administrator of thedata processing system, the second subset including action-inventoriesprovided by an agent service handling one of the plurality ofapplications.

The action handler may provide the action data structure to the secondapplication to cause the second application to parse the action datastructure to identify the action to be executed, generate the output byexecuting the action identified from the action data structure andprovide the output for the user interface component to be presented withthe graphical user interface of the first application authorized to bepresented with the second application.

According to a second aspect of the disclosure, a method of renderingvisual components on applications. A data processing system having oneor more processors can maintain a plurality of action-inventories for aplurality of applications. At least one of the plurality ofaction-inventories can indicate to render a user interface component forone of the plurality of applications in executing an action. The dataprocessing system can receive a data packet comprising an input audiosignal detected by a sensor of a client device. The client device candisplay a graphical user interface of a first application in aforeground process on the client device. The data processing system canparse the input audio signal of the data packet to identify a request.The data processing system can select, from the plurality ofaction-inventories, an action-inventory that executes the actioncorresponding to the request by a second application of the plurality ofapplications. The second application can be installed on the clientdevice and not in the foreground process. The data processing system cangenerate an action data structure in accordance with theaction-inventory. The data processing system can provide the action datastructure to the second application to cause the second application toparse the action data structure and execute the action to generate anoutput. The data processing system can determine that the output of thesecond application from execution of the action is authorized to bepresented with the graphical user interface of the first applicationbased on an authorization policy of the second application. The dataprocessing system can identify the user interface component of thesecond application for the action-inventory selected from the pluralityof action-inventories, responsive to the determination the output of thesecond application is authorized to be presented with the firstapplication. The data processing system can display, on the clientdevice, the user interface component including the output from thesecond application with the graphical user interface of the firstapplication authorized to be presented with the second application.

Optional features of the first aspect described above or in the detaileddescription below may be combined with the second aspect.

These and other aspects and implementations are discussed in detailbelow. The foregoing information and the following detailed descriptioninclude illustrative examples of various aspects and implementations andprovide an overview or framework for understanding the nature andcharacter of the claimed aspects and implementations. The drawingsprovide illustration and a further understanding of the various aspectsand implementations, and are incorporated in and constitute a part ofthis specification.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Likereference numbers and designations in the various drawings indicate likeelements. For purposes of clarity, not every component may be labeled inevery drawing. In the drawings:

FIG. 1 illustrates a block diagram of an example system to render visualcomponents on applications in response to voice input commands, inaccordance with an example of the present disclosure.

FIG. 2 illustrates a sequence diagram of an example data flow to rendervisual components on applications in response to voice input commands inthe system illustrated in FIG. 1, in accordance with an example of thepresent disclosure.

FIG. 3 illustrates a use case diagram of an example client devicedisplaying input messages and generating addresses in the systemillustrated in FIG. 1, in accordance with an example of the presentdisclosure.

FIG. 4 illustrates a flow diagram of a method to render visualcomponents on applications in response to voice input commands using theexample system illustrated in FIG. 1, in accordance with an example ofthe present disclosure.

FIG. 5 is a block diagram of an example computer system.

DETAILED DESCRIPTION

Following below are more detailed descriptions of various conceptsrelated to and implementations of, methods, apparatuses, and systems torender visual components on applications in response to voice inputcommands. The various concepts introduced above and discussed in greaterdetail below may be implemented in any of numerous ways.

Multiple applications can be installed on a client device to carry outpreconfigured functions as requested by a user operating the clientdevice. At a given time, the client device can run a subset of theseapplications as a foreground process or a non-foreground process as setby an operating system running on client device. Foreground processes(including visible processes) can correspond to applications with agraphical user interface presented on a display of the client devicewith which the user may be interacting. Non-foreground processes (e.g.,a service process, a background process, or a cached process) cancorrespond to applications not displaying visual components to the userand executing without affecting the graphical user interface of theforeground process. The applications running on the client device canswitch back and forth between executing as a foreground process ornon-foreground process. Upon switching, the graphical user interface ofthe application that was previously the foreground process can bereplaced by the graphical user interface of the application that is nowset as the foreground process. In addition, the processing and memoryallocations can change as a result of the switching between foregroundand non-foreground processes.

One of these applications running in the foreground or thenon-foreground can include a digital assistant application. Unlike atleast some of the other applications installed on the client device, thedigital assistant application can have natural language processingcapabilities. Configured with these capabilities, the digital assistantapplication can acquire and parse an input audio signal detected via amicrophone of the client device to recognize words from the input audiosignal. From the recognized words, the digital assistant application candetermine a request to be carried out and one or more parametersdefining the request. The request can refer to one of the preconfiguredfunctions with input arguments compatible with the parameters that canbe executed by the digital assistant application (e.g., retrievingresults for a search query). For such requests, the digital assistantapplication itself can process the request and present an audio orvisual output from carrying out the request. Some requests, however, maynot correspond to any of the functions preconfigured on the digitalassistant application (e.g., playing a video from an online videoplatform). For these types of requests, the digital assistantapplication can identify another application that is capable of carryingout the request and invoke the function of the application to passparameters.

By invoking the other application to carry out the request, the digitalassistant application can cause a change in which applications areforeground and non-foreground processes, resulting in a shift in thegraphical user interface displayed on the client device. In addition,the processing and memory allocations to each executing application canchange and fluctuate, especially when invoking a previouslynon-executing application. While the desired request may be eventuallycarried out on the client device with the invoked application, theswitch can interfere with the overall user experience with theapplications on the client device. For example, the sudden alteration inthe graphical user interface displayed on the client device can forcethe user to under context switching between the interfaces of multipleapplications, thereby degrading human-computer interactions (HCI) withthe client device. The degradation in the client device can also beexacerbated by change and fluctuation in the new allocations ofcomputing resources in performing the switching of foreground andnon-foreground processes.

The present disclosure provides an improved user interface. Inparticular, to address the technical challenges in interfacing, thepresent disclosure can provide action-inventories used to identify andpresent user interface components to be overlaid on the graphical userinterfaces of applications in the foreground. The action-inventory canspecify whether to provide a user interface element of the applicationwhile maintaining the application in the background. Theaction-inventory can also include an address template to construct anaddress for accessing a function of the digital assistant applicationand for providing the user interface element on the client device. Theaddress template of an action-inventory may be, for example, a UniformResource Identifier (URI) template for constructing a web address with ahostname, pathname, and queries to invoke a function of an applicationand for the user interface component. The hostname (or a scheme) canreference a location or a domain name of the application. The pathnamecan reference the function. The queries can include one or more inputarguments used to carry out the function. The address template can alsodefine a mapping of the request parsed from input audio signals tofunctions to be executed by the application.

Upon the recognition of the request from the input audio signal, thedigital assistant application can determine that the request does notcorrespond with any of the functionalities of the digital assistantapplication or to any application running as the foreground process.Instead of outputting that the digital assistant application cannotperform the indicated request, the digital assistant application canidentify another application to carry out the function. While processingthe request, the digital assistant application can remain as abackground process with the original application remaining as theforeground process. With the identification, the digital assistantapplication can select an action-inventory of the application for thefunction. The selected action-inventory can indicate that a userinterface component of the application is to be presented. Using theaction-inventory, the digital assistant application can construct,expand, and generate the address for the function in accordance with theaddress template. The address can include the hostname (or scheme)referencing the application, the path referencing the function and theuser interface component, and one or more queries including theparameters.

With the generation of the address in accordance with the addresstemplate, the digital assistant application can generate and pass anaction data structure (e.g., an API function call) including the addressto the application. The application to which the action data structureis passed can be opened as a background process, and remain in thebackground process as the action is processed and completed. The passingof the action data structure to the other application can be performedas the original application continues to remain as the foregroundprocess. For example, the action data structure can be passed by anoperating system on the client device from the digital assistantapplication to the application via the API function call. As the addressincludes the hostname referencing the application, the action datastructure can be directed to reach the referenced application. Uponreceipt, the application can parse the action data structure to identifythe address. The application can further parse the address to identifythe pathname to identify the function to be executed and parse thestring query to identify the one or more parameters to define theexecution of the function. Based on the identification, the applicationcan execute the function to generate an output. Using the outputgenerated by the application, the digital assistant can render the userinterface component of the application. The user interface component ofthe application can be overlaid on the graphical user interface of theapplication of the foreground process.

In this manner, the digital assistant application can invoke thefunctions of other applications and present rendering of the userinterface components from these applications, thereby augmenting thefunctions of the digital assistant application. The invocation may beperformed without the user manually searching, opening, and entering toachieve the desired function, or having to context switch betweendifferent applications. The elimination of context switching on the partof the user operating the client device can thus improve HCI.Furthermore, the applications can remain in the foreground andnon-foreground processes, even with the recognition of a request fromthe input audio signal. As the switching between foreground andbackground processes is eliminated, the digital assistant applicationcan reduce consumption of computing resources and expenditure of time onthe part of the user.

Referring to FIG. 1, depicted is an example system 100 to render visualcomponents on applications. The system 100 can include at least one dataprocessing system 102, at least one client device 104, and at least oneagent services 106. The data processing system 102, the client device104, and the agent service 106 can be communicatively coupled with oneanother via at least one network 114.

The components of the system 100 can communicate over a network 114. Thenetwork 114 can include, for example, a point-to-point network, abroadcast network, a wide area network, a local area network, atelecommunications network, a data communication network, a computernetwork, an ATM (Asynchronous Transfer Mode) network, a SONET(Synchronous Optical Network) network, a SDH (Synchronous DigitalHierarchy) network, an NFC (Near-Field Communication) network, a localarea network (LAN), a wireless network or a wireline network, andcombinations thereof. The network 114 can include a wireless link, suchas an infrared channel or satellite band. The topology of the network114 may include a bus, star, or ring network topology. The network 114can include mobile telephone networks using any protocol or protocolsused to communicate among mobile devices, including advanced mobilephone protocol (AMPS), time division multiple access (TDMA),code-division multiple access (CDMA), global system for mobilecommunication (GSM), general packet radio services (GPRS), or universalmobile telecommunications system (UMTS). Different types of data may betransmitted via different protocols, or the same types of data may betransmitted via different protocols.

The data processing system 102 and the agent service 106 each caninclude multiple, logically grouped servers and facilitate distributedcomputing techniques. The logical group of servers may be referred to asa data center, server farm, or a machine farm. The servers can begeographically dispersed. A data center or machine farm may beadministered as a single entity, or the machine farm can include aplurality of machine farms. The servers within each machine farm can beheterogeneous—one or more of the servers or machines can operateaccording to one or more type of operating system platform. The dataprocessing system 102 and the agent service 106 each can include serversin a data center that are stored in one or more high-density racksystems, along with associated storage systems, located for example inan enterprise data center. In this way, the data processing system 102or the agent service 106 with consolidated servers can improve systemmanageability, data security, the physical security of the system, andsystem performance by locating servers and high performance storagesystems on localized high performance networks. Centralization of all orsome of the data processing system 102 or agent service 106 components,including servers and storage systems, and coupling them with advancedsystem management tools allows more efficient use of server resources,which saves power and processing requirements and reduces bandwidthusage. Each of the components of the data processing system 102 caninclude at least one processing unit, server, virtual server, circuit,engine, agent, appliance, or other logic device such as programmablelogic arrays configured to communicate with the data repositories 128and with other computing devices. The agent service 106 can also includeat least one processing unit, server, virtual server, circuit, engine,agent, appliance, or other logic device such as programmable logicarrays configured to communicate with a data repository and with othercomputing devices.

The data processing system 102 can include an instance of at least onedigital assistant application 108. The digital assistant application 108can include at least one natural language processor (NLP) component 116(sometimes referred herein as an natural language processor) to parseaudio-based inputs. The digital assistant application 108 can include atleast one audio signal generator component 118 (sometimes referredherein as an audio signal generator) to generate audio-based signals.The digital assistant application 108 can include at least one actionhandler component 120 (sometimes referred herein as an action handler)to generate action data structures based on the audio-based inputs. Thedigital assistant application 108 can include at least one responseselector component 122 to select responses to audio-based input signals.The digital assistant application 108 can include at least one agentregistry component 124 (sometimes referred herein as an agent registry)to maintain action-inventories for generating the action datastructures. The digital assistant application 108 can include at leastone agent interface component 126 (sometimes referred herein as agentinterface) to communicate with one or more agent applications 110.

The digital assistant application 108 can include at least one datarepository 128. The data repository 128 of the data processing system102 can include one or more local or distributed databases and caninclude a database management system. The data repository 128 caninclude one or more regular expressions 130, one or more data parameters132, one or more policies 134, one or more response data 136, one ormore templates 138, and one or more action inventories 140. The NLPcomponent 116, the audio signal generator component 118, the actionhandler component 120, the response selector component 122, the agentregistry component 124, the agent interface component 126, and the datarepository 128 can be separate from one another. The data repository 128can include computer data storage or memory and can store the one ormore regular expressions 130, one or more data parameters 132, one ormore policies 134, response data 136, templates 138, and the one or moreaction-inventories 140 among other data. The data parameters 132,policies 134, and templates 138 can include information such as rulesabout a voice-based session between the client devices 104 and the dataprocessing system 102. The response data 136 can include content itemsfor audio output or associated metadata, as well as input audio messagesthat can be part of one or more communication sessions with the clientdevices 104. The action-inventories 140 can include information toinvoke or interface with the agent application 110.

The data processing system 102 can include an instance of at least oneagent application 110 (also referred herein as “agent” or “application”)to execute various functions. The agent service 106 can include aninstance of at least one agent application 110 to execute variousfunctions. The agent application 110 can lack natural languageprocessing capabilities (such as those provided by the NLP component116). The agent application 110 can also have a preconfigured or apredetermined set of input capabilities. The input capabilities of theagent application 110 can include, for example, inputs from a mouse, akeyboard, a touch screen (e.g., a display 148), or a camera of theclient device 104. The input capabilities of the agent application 110can lack audio (e.g., a microphone 146) from the client device 104. Theagent application 110 can have a graphical user interface (GUI) toreceive the inputs from the client device 104. Based on the input fromthe predetermined input capabilities, the agent application 110 cancarry out or execute one or more functions. For example, the agentapplication 110 can be a coffee purchase application, and can have agraphical user interface with one or more element to specify an order ofa coffee. In this application, a user operating the client device 104can manually enter the coffee, size, and billing information, amongothers, on the graphical user interface rendered on the display 148 ofthe client device 104. Once set, the agent application 110 on the clientdevice 104 can send the input via the network 114 to the agent service106. The agent service 106 in turn can carry out the purchase orderindicated by the inputs entered through the graphical user interface ofthe agent application 110.

The components of the data processing system 102 can each include atleast one processing unit or other logic device such as a programmablelogic array engine or module configured to communicate with the datarepository 128. The components of the data processing system 102 can beseparate components, a single component, or part of multiple dataprocessing systems 102. The system 100 and its components, such as adata processing system 102, can include hardware elements, such as oneor more processors, logic devices, or circuits.

The functionalities of the data processing system 102, such as thedigital assistant application 108 or the agent application 110, can beincluded or otherwise be accessible from the one or more client devices104. The functionalities of the data processing system 102 maycorrespond to the functionalities or interface with the digitalassistant application 108 executing on the client devices 104. Theclient devices 104 can each include and execute a separate instance ofthe one or more components of the digital assistant application 108. Theclient devices 104 can otherwise have access to the functionalities ofthe components of the digital assistant application 108 on a remote dataprocessing system 102 via the network 114. For example, the clientdevice 104 can include the functionalities of the NLP component 116 andaccess the remainder of the components of the digital assistantapplication 108 via the network 114 to the data processing system 102.The functionalities of the data processing system 102 may correspond tothe functionalities or interface with the agent application 110executing on the client devices 104. The client devices 104 canotherwise have access to the functionalities of the components of theagent application 110 on the data processing system 102 or the agentservice 106 via the network 114. For example, the client device 104 canpre-process input from the mouse, keyboard, touchscreen, or camera forthe agent application 110, and provide the input to the agent service106 to carry out the function of the agent application 110. The digitalassistant application 108 executing on the client device 104 can includethe functionalities of the digital assistant application 108 executingon the data processing system 102.

The client device 104 can each include at least one logic device such asa computing device having a processor to communicate with each otherwith the data processing system 102 via the network 114. The clientdevices 104 can include an instance of any of the components describedin relation to the data processing system 102 or the agent service 106.The client device 104 can include an instance of the digital assistantapplication 108. The client device 104 can include an instance of theagent application 110. The client devices 104 can include a desktopcomputer, laptop, tablet computer, personal digital assistant,smartphone, mobile device, portable computer, thin client computer,virtual server, speaker-based digital assistant, or other computingdevice.

The client device 104 can include, execute, interface, or otherwisecommunicate with one or more of at least one instance of the digitalassistant application 108, at least one instance of the agentapplication 110, and at least one communications interface 112, amongothers. In addition, the client device 104 can include, interface, orotherwise communicate with at least one speaker 144, at least onemicrophone 146, and at least one display 148. The client device 104 caninclude an audio driver to provide a software interface with the speaker144 and the microphone 146. The audio driver can execute instructionsprovided by the data processing system 102 to control the speaker 144 togenerate a corresponding acoustic wave or sound wave. The audio drivercan execute an audio file or other instructions to convert an acousticwave or sound wave acquired from the microphone 146 to generate audiodata. For example, the audio driver can execute an analog-to-driverconverter (ADC) to transform the acoustic wave or sound wave to theaudio data. The client device 104 can include a graphics driver toprovide a software interface with the display 148. The graphics drivercan execute instructions provided by the data processing system 102 orthe agent service 106 to control the display 148 to generate acorresponding rendering thereon.

The instance of the digital assistant application 108 on the clientdevice 104 can include or be executed by one or more processors, logicarray, or memory. The instance of the digital assistant application 108on the client device 104 can detect a keyword and perform an actionbased on the keyword. The digital assistant application 108 on theclient device 104 can be an instance of the digital assistantapplication 108 executed at the data processing system 102 or canperform any of the functions of the digital assistant application 108.The instance of the digital assistant application 108 on the clientdevice 104 can filter out one or more terms or modify the terms prior totransmitting the terms as data to the data processing system 102 (e.g.,the instance of the digital assistant application 108 on the dataprocessing system 102) for further processing. The instance of thedigital assistant application 108 on the client device 104 can convertthe analog audio signals detected by the speaker 144 into a digitalaudio signal and transmit one or more data packets carrying the digitalaudio signal to the data processing system 102 via the network 114. Theinstance of the digital assistant application 108 on the client device104 can transmit data packets carrying some or the entire input audiosignal responsive to detecting an instruction to perform suchtransmission. The instruction can include, for example, a triggerkeyword or other keyword or approval to transmit data packets comprisingthe input audio signal to the data processing system 102.

The instance of the digital assistant application 108 on the clientdevice 104 can perform pre-filtering or pre-processing on the inputaudio signal to remove certain frequencies of audio. The pre-filteringcan include filters such as a low-pass filter, high-pass filter, or abandpass filter. The filters can be applied in the frequency domain. Thefilters can be applied using digital signal processing techniques. Thefilter can keep frequencies that correspond to a human voice or humanspeech, while eliminating frequencies that fall outside the typicalfrequencies of human speech. For example, a bandpass filter can removefrequencies below a first threshold (e.g., 70 Hz, 75 Hz, 80 Hz, 85 Hz,90 Hz, 95 Hz, 100 Hz, or 105 Hz) and above a second threshold (e.g., 200Hz, 205 Hz, 210 Hz, 225 Hz, 235 Hz, 245 Hz, or 255 Hz). Applying abandpass filter can reduce computing resource utilization in downstreamprocessing. The instance of the digital assistant application 108 on theclient device 104 can apply the bandpass filter prior to transmittingthe input audio signal to the data processing system 102, therebyreducing network bandwidth utilization. However, based on the computingresources available to the client device 104 and the available networkbandwidth, it may be more efficient to provide the input audio signal tothe data processing system 102 to allow the data processing system 102to perform the filtering. The instance of the digital assistantapplication 108 on the client device 104 can apply additionalpre-processing or pre-filtering techniques such as noise reductiontechniques to reduce ambient noise levels that can interfere with thenatural language processor. Noise reduction techniques can improveaccuracy and speed of the natural language processor, thereby improvingthe performance of the data processing system 102 and manage renderingof a graphical user interface provided via the display.

The client device 104 can be operated by an end user that enters voicequeries as audio input into the client device 104 (via the microphone146 or speaker 144) and receives audio (or other) output from the dataprocessing system 102 or agent services 106 to present, display, orrender to the end user of the client device 104. The digital componentcan include a computer-generated voice that can be provided from thedata processing system to the client device 104. The client device 104can render the computer-generated voice to the end user via the speaker144. The computer-generated voice can include recordings from a realperson or computer-generated language. The client device 104 can providevisual output via the display 148 communicatively coupled to the clientdevice 104.

The client device 104 can have or execute as at least one foregroundprocess 150 (also referred herein as a foreground service). Theforeground process 150 can correspond to at least one of theapplications (e.g., the digital assistant application 108 or an agentapplication 110) that is rendered on the display 148 and executing onthe client device 104. For example, the foreground process 150 cancorrespond to an application with a graphical user interface occupying amajority of the display 148. The application running on the clientdevice 104 as the foreground process 150 can have a graphical userinterface rendered on the display 148 of the client device 104. Thegraphical user interface of the application in the foreground process150 can occupy at least a portion of the display 148 of the clientdevice 104 (e.g., at least a third the display 148). The applicationrunning on the client device 104 as the foreground process 150 can waitfor user interactions with the graphical user interface (e.g., via theI/O devices communicatively coupled with the client device 104) to carryout one or more routines. The application in the foreground process 150can process the user interactions to carry out the one or more routinesof the application. In the processing of the user interactions, theapplication in the foreground process 150 can generate an output and canrender the resultant output on the graphical user interface of theapplication in the foreground process 150.

The client device 104 can have or execute at least one non-foregroundprocess 152 (also referred herein as a background process, a backgroundservice, non-foreground process, or a non-foreground service). Thenon-foreground process 152 can correspond to at least at least one ofthe applications (e.g., the digital assistant application 108 or anotheragent application 110) that is not rendered on the display 148 andexecuting on the client device 104. The application running on theclient device 104 as the non-foreground process 152 can lack anyrendering of the graphical user interface of the application on thedisplay 148 of the client device 104. For example, the non-foregroundprocess 152 can correspond to an application that is minimized andwithout any graphical user interface component rendered in the display148. The application running on the client device 104 as thenon-foreground process 152 can execute one or more routines withoutreceipt of any user interactions with the application. For example, anapplication running as the non-foreground process 152 can process audiodetected on the microphone 146 of the client device 104, without havingany graphical user interface rendered on the display 148. In theprocessing of the user interactions, the application in the foregroundprocess 150 can generate an output without rendering the resultantoutput as a part of the graphical user rendered on the display 148.

The client device 104 can manage the applications in the foregroundprocess 150 and the non-foreground process 152 (e.g., using an operatingsystem executing on the client device 104). The client device 104 canswitch applications between the foreground process 150 and thenon-foreground process 152. The switch of the applications between theforeground process 150 and the non-foreground process 152 can be inresponse to an invocation of at least one application. The invokedapplication can be running in the non-foreground process 152 or inneither the foreground process 150 and the non-foreground process 152.The invocation can be by the operating system executing on the clientdevice 104, by another application (e.g., the digital assistantapplication 108 or the agent application 110), or by a user interactionevent. In response to the invocation, the client device 104 can set anapplication running in the foreground process 150 to the non-foregroundprocess 152. In addition, the client device 104 can set an applicationrunning in the non-foreground process 152 to the foreground process 150.When the invoked application is not running as the non-foregroundprocess 152, the client device 104 can also instantiate the applicationinto the foreground process 150. For example, a web browser can beexecuting on the client device 104 as the foreground process 150 with agraphical user interface rendered on the display 148. A clockapplication can be running on the client device 104 as thenon-foreground process 152 to track time, without the rendering of anygraphical user interface rendered on the display 148. Upon theinvocation of an alarm function of the clock application, the clientdevice 104 can set the web browser as the non-foreground process 152thereby removing the rendering of the graphical user interface of theweb browser. In conjunction, the client device 104 can set the clockapplication as the foreground process 150.

The data processing system 102 and the agent service 106 each caninclude at least one server having at least one processor. For example,the data processing system 102 and the agent service 106 each caninclude a plurality of servers located in at least one data center orserver farm. The data processing system 102 can include at least onecomputation resource or server. The data processing system 102 caninclude, interface, or otherwise communicate with at least onecommunications interface 112. The data processing system 102 caninclude, interface, or otherwise communicate with at least one instanceof the digital assistant application 108 on the data processing system102. The instance of the digital assistant application 108 on the dataprocessing system 102 can include, interface, or otherwise communicatewith: the at least one NLP component 116, the at least one audio signalgenerator component 118, at least one action handler component 120, theat least one response selector component 122, the at least one agentregistry component 124, and the at least one agent interface component126, among others. The data processing system 102 can include,interface, or otherwise communicate with at least one data repository128. The at least one data repository 128 can include or store, in oneor more data structures or databases, regular expressions 130, dataparameters 132, policies 134, response data 136, templates 138, andaction-inventories 140. The data repository 128 can include one or morelocal or distributed databases, and can include a database management.

The instance of digital assistant application 108 of the data processingsystem 102 can execute or run an instance of the agent registrycomponent 124 to maintain the set of action-inventories 140 on the datarepository 128. The agent registry component 124 can maintain and storethe set of action-inventories 140 for one or more agent applications 110on the data repository 128. A subset of the action-inventories 140 canbe defined by an administrator of the data processing system 102 or thedigital assistant application 108 for an application type correspondingto the agent application 110. For example, the administrator of thedigital assistant application 108 can configure or define a built-in setof action-inventories 140 for purchase order applications. Anothersubset of action-inventories 140 can be provided by one of the agentservices 106 handling resources for the corresponding agent application110. At least one of the action-inventories 140 can be a presetaction-inventory 140 to be used to carry out an action, in response todetermining that a request does not match any other action-inventory 140of the agent application 110. For example, the agent service 106 canprovide a set of customized action-inventories 140 to the dataprocessing system 102 for storage onto the data repository 128. Theagent registry component 124 can receive the subset ofaction-inventories 140 provided by the agent service 106. Upon receipt,the agent registry component 124 can store the receivedaction-inventories 140 onto the data repository 128. The existence ofthe action-inventory 140 for the action of the agent application 110 onthe data repository 128 can indicate that the agent application 110 iscapable of performing the action corresponding to the action-inventory140.

The agent registry component 124 can maintain and store a set of userinterface components 142 for one or more agent applications 110 on thedata repository 128. Each user interface component 142 can be associatedwith at least one of the action-inventories 140. A subset of the userinterface components 142 can be defined by an administrator of the dataprocessing system 102 or the digital assistant application 108. Forexample, the administrator of the digital assistant application 108 canconfigure or define a built-in set of user interface components 142.Another subset of user interface components 142 can be provided by oneof the agent services 106 handling resources for the corresponding agentapplication 110. The agent service 106 can store and maintain the userinterface component 142 corresponding to the subset. For example, theagent service 106 can provide a set of customized user interfacecomponents 142 to the data processing system 102 for storage onto thedata repository 128. The agent registry component 124 can receive thesubset of user interface components 142 provided by the agent service106. Upon receipt, the agent registry component 124 can store thereceived user interface components 142 onto the data repository 128. Themaintenance of the user interface components 142 by the agent service106 can be separate from the maintenance of the user interface component142 on the data repository 128.

Each user interface component 142 can have one or more interfaceelements. Each interface element can correspond to a subcomponent of theuser interface component 142. At least one interface element cancorrespond to a request to be identified from input audio signalsdetected by the microphone 146 of the client device 104. At least oneinterface element can correspond to a response indicating an outputgenerated by the agent application 110 associated with the userinterface component 142. Furthermore, each user interface component canhave one or more properties. The properties can include an element type(e.g., command button, scroll bar, textbox, and image), a size, alocation within the user interface component 142, transparency, andshape, among others. For example, a user interface component 142 canhave a button located generally along the bottom, a textbox above thebutton, and a slot for an image generally in the middle, among others.The user interface component 142 itself can have one or more properties.The properties of the user interface component 142 can include a size, alocation within the display 148, transparency, and shape, among others.

Each action-inventory 140 can have at least one address template for atleast one action by one of the agent applications 110. The addresstemplate may be for a single action of the agent application 110 ormultiple actions to be carried by the agent application 110. The addresstemplate may be also for accessing or retrieving the user interfacecomponent 142 to be generated in carrying out the action. The addresstemplate for the action can include a first portion and a secondportion. The address template can be, for example, a Uniform ResourceIdentifier (URI) template in accordance to which an URI is to begenerated. The first portion of the address template can correspond toone of the agent applications 110 or the agent service 106 providingresources for the agent application 110. For example, the first portionof the address template can include a scheme in a custom deep-link URIreferencing the agent application 110. The first portion of the addresstemplate can also include a hostname referencing the agent service 106.

The second portion of the address template can correspond to the actionthat is to be performed by the agent application 110. The second portionof the address template can also include one or more input variables(also referred herein as input arguments of fields) used to execute theaction. For example, the second portion of the address template caninclude a pathname in a URI corresponding to the action to be taken. Thesecond portion can also include one or more query strings following thepathname in the URI. Each query string can correspond to one of theinput variables used to execute the action. A subset of the inputvariables can include optional or auxiliary input variables. The actioncan be executed by the agent application 110 without the auxiliary inputvariables in the address.

The action-inventory 140 can include a mapping (sometimes referredherein as a parameter mapping) for the second portion of the addresstemplate. The mapping can specify or define a correspondence between atleast one input variable of the second portion and one or more words tobe identified from parsing input audio signals. The one or more wordsfrom parsing input audio signals can correspond to the input variablesdefining the action to be executed by the agent application 110. Themapping can define the insertion of the words into the input variablesof the address template. For example, the mapping for a coffee purchaseorder action can specify insertion of a coffee name parsed from theaudio signal to a coffee input variable of the address template. Theaction-inventory 140 can specify or include a set of permitted values(sometimes referred as an entity-inventory) for each input variable. Theset of permitted values can be a part of the mapping for theaction-inventory 140. For example, the permitted values for a coffeepurchase order can include “latte,” “café latte,” and “latte coffee,”and the like for an input variable for the coffee name. Theaction-inventory 140 can also include a marker indicating acorresponding input variable of the address template as optional orauxiliary. The marker can be part of the mapping for the second portionof the address template.

In addition to the address template, each action-inventory 140maintained by the agent registry component 124 can include informationrelated to the action for the action-inventory 140. The action-inventory140 can include an interface mode indicator. The indicator can specifywhether the user interface component 142 of the agent application 110 isto be displayed in carrying out the action. The user interface component142 can be a visual element to be rendered in the display 148 of theclient device 104. The user interface component 142 can have a size lessthan a size of the display 148. For example, the user interfacecomponent 142 can include a box-sized visual element to occupy a 12.5%to 25% of the display 148. The user interface component 142 can beassociated with at least one of the action-inventories 140 maintained onthe data repository 128.

The user interface component 142 can be associated with theaction-inventory 140. The action-inventory 140 can include an addressreferencing the user interface component 142. The address referencingthe user interface component 142 can differ or be separate from theaddress template for executing the action. The address referencing theuser interface component 142 can have the same scheme or hostname as theaddress template for the same action-inventory 140. For example, theaddress can include the hostname of the agent service 106 managingresources for the agent application 110. The address referencing theuser interface component 142 can have a different hostname as theaddress template of the same action-inventory 140. For example, thehostname can reference the data repository 128 of the data processingsystem 102. The action-inventory 140 can also include an user interfaceidentifier corresponding to the user interface component 142. Theidentifier may be used to index and reference the user interfacecomponent 142 maintained on the data repository 128. In addition, theaddress template of the action-inventory 140 can be used to referencethe user interface component 142 along with the action to be executed bythe agent application 110.

The action-inventory 140 can also include at least one agent identifiercorresponding to one of the agent applications 110 to carry out theaction. The agent identifier can include a set of alphanumericcharacters referencing the agent application 110. The agent identifiercan be used to identify the agent application 110 associated with theaction-inventory 140 from words parsed from input audio signals. Theaction-inventory 140 can include at least one request identifiercorresponding to the action to be carried by the agent application 110.The request identifier (sometimes referred herein as an “intentidentifier” or “intent name”) can include a set of alphanumericcharacters referencing the action to be carried out. The addresstemplate can be uniquely identified by one or more request identifiers.The request identifier can be used to identify the action-inventory 140from words parsed from input audio signals.

Each action-inventory 140 can be implemented or specified using a markuplanguage, such as an Extensible Markup Language (XML) file. For example,the action-inventory 140 can be an XML file of the following form:

<actions>  <action intentName=“actions.intent.CHECK_STEPS” >  <fulfillment    fulfillmentMode=“actions.fulfillment.SLICE”   urlTemplate=“https://ex_personalmetrics.example.com/checksteps{?username}”>   <parameter-mapping   intentParameter=“user.name”    urlParameter=“username”   required=“true” />   </fulfillment>   <fulfillment urlTemplate =“https://ex_personalmetrics.example.com/ checksteps” />  </action></actions>In the example above, the action-inventory 140 can be for an order rideto be executed by a personal fitness application. The entry“actions.intent.CHECK_STEPS” may correspond to the request identifierfor the action-inventory 140. The entry “actions.fulfillment.SLICE” canspecify the display of the user interface component 142 associated withthe action-inventory 140. The entry“https://ex_personalmetrics.example.com/checksteps{?username}” cancorrespond to the address template, in which“https://ex_personalmetrics.example.com/ corresponds to the firstportion and “checksteps{?username}” corresponds to the second portion.The entry starting with “parameter-mapping” may correspond to themapping. Lastly, the entry “https://ex_personalmetrics.example.com/checksteps” can correspond to a separate address forthe user interface component 142.

The agent registry component 124 can construct, create, or generate theset of action-inventories 140 for each agent application 110. The agentservice 104 for the agent application 110 can provide a configurationfile associated with the agent application 110 to the agent registrycomponent 124 via the network 114. The configuration file can be, forexample, an application binary interface (ABI) for the agent application110 submitted by an application developer associated with the agentapplication 110 to the agent registry component 124. The agent service104 for the agent application 110 can provide metadata associated withthe agent application 110. The metadata can include the agent identifierand an application type to the agent registry component 124, amongothers. The application type can indicate a usage of the agentapplication 110. The agent service 104 for the agent application 110 canprovide the interface mode indicator for one or more actions capable ofbeing executed by the agent application 110. The agent registrycomponent 124 can receive the information from the agent service 106 forthe generation of the set of action-inventories 140 of the agentapplication 110.

The agent registry component 124 can read, ingest, and parse theconfiguration file for the agent application 110 to identify one or moreactions. For each identified function, the agent registry component 124can generate an action-inventory 140 for the action. The action can beone of the actions of the set of action-inventories 140 defined by theadministrator of the data processing system 102 or the digital assistantapplication 108 for the application type of the agent application 110.The agent registry component 1240 generate the address template for theaction to be executed by the agent application 110. The first portion ofthe address template (e.g., the hostname or scheme) can correspond tothe agent application 110. The second portion of the address templatecan be predefined for the action (e.g., using a preset pathname or aquery string). The agent registry component 124 can also generate amapping for the action-inventory 140 for the identified function. Theagent registry component 124 can include or add a request identifiercorresponding to the identified action into the action-inventory 140.The mapping can include the set of permitted values for the inputvariables of the address template. The agent registry component 124 caninclude or add an agent identifier corresponding to the agentapplication 110 into the action-inventory 140. With the construction ofthe action-inventory 140, the agent registry component 124 can store theaction-inventory 140 onto the data repository 128.

The data processing system 102 can include at least one communicationsinterface 112. The communications interface 112 can be configured,constructed, or operational to receive and transmit information using,for example, data packets. The communications interface 112 can receiveand transmit information using one or more protocols, such as a networkprotocol. The communications interface 112 can include a hardwareinterface, software interface, wired interface, or wireless interface.The communications interface 112 can be a data interface or a networkinterface that enables the components of the system 100 to communicatewith one another. The communications interface 112 of the dataprocessing system 102 can provide or transmit one or more data packetsthat include the action data structure, audio signals, or other data viathe network 114 to the client devices 104 or the agent service 106. Forexample, the data processing system 102 can provide the output signalfrom the data repository 128 or from the audio signal generatorcomponent 118 to the client devices 104.

The data processing system 102 can also instruct, via data packettransmissions, the client devices 104 to perform the functions indicatedin the action data structure. The output signal can be obtained,generated, transformed to, or transmitted as one or more data packets(or other communications protocol) from the data processing system 102(or other computing device) to the client devices 104. Thecommunications interface 112 can facilitate translating or formattingdata from one format to another format. For example, the communicationsinterface 112 can include an application programming interface (“API”)that includes definitions for communicating between various components,such as software components. An application, script, program, or othercomponents that are associated with the data processing system 102 canbe installed at the client devices 104. The application can enabled theclient devices 104 to communicate input audio signals (and other data)to the communications interface 112 of the data processing system 102.

The data processing system 102 can include an application, script, orprogram installed at the client device 104, such as the instance of thedigital assistant application 108 on the client device 104 tocommunicate input audio signals to the communications interface 112 ofthe data processing system 102 and to drive components of the clientcomputing device to render output audio signals or visual output. Thedata processing system 102 can receive data packets, a digital file, orother signals that include or identify an input audio signal (or inputaudio signals). The client device 104 can detect the audio signal viathe speaker 144 and convert the analog audio signal to a digital filevia an analog-to-digital converter. For example, the audio driver caninclude an analog-to-digital converter component. The pre-processorcomponent can convert the audio signals to a digital file that can betransmitted via data packets over network 114.

The instance of the digital assistant application 108 of the dataprocessing system 102 or the client device 104 can execute or run an NLPcomponent 116 to receive or obtain the data packets including the inputaudio signal detected by the microphone 146 of the client device 104.The data packets can provide a digital file. The NLP component 116 canreceive or obtain the digital file or data packets comprising the audiosignal and parse the audio signal. For example, the NLP component 116can provide for interactions between a human and a computer. The NLPcomponent 116 can be configured with techniques for understandingnatural language and enabling the data processing system 102 to derivemeaning from human or natural language input. The NLP component 116 caninclude or be configured with techniques based on machine learning, suchas statistical machine learning. The NLP component 116 can utilizedecision trees, statistical models, or probabilistic models to parse theinput audio signal.

The NLP component 116 can perform, for example, functions such as namedentity recognition (e.g., given a stream of text, determine which itemsin the text map to names, such as people or places, and what the type ofeach such name is, such as person, location (e.g., “home”), ororganization), natural language generation (e.g., convert informationfrom computer databases or semantic intents into understandable humanlanguage), natural language understanding (e.g., convert text into moreformal representations such as first-order logic structures that acomputer module can manipulate), machine translation (e.g.,automatically translate text from one human language to another),morphological segmentation (e.g., separating words into individualmorphemes and identify the class of the morphemes, which can bechallenging based on the complexity of the morphology or structure ofthe words of the language being considered), question answering (e.g.,determining an answer to a human-language question, which can bespecific or open-ended), or semantic processing (e.g., processing thatcan occur after identifying a word and encoding its meaning in order torelate the identified word to other words with similar meanings).

The NLP component 116 (and the digital assistant application 108 as awhole) can execute as one of the applications in the non-foregroundprocess 152. When the input audio signal is detected on the microphone146, the client device 104 can continue to the digital assistantapplication 108 as one of the applications in the non-foreground process152. The client device 104 can have one or more other applications(e.g., an agent application 110) running as the non-foreground processes152. Furthermore, the client device 104 can have at least oneapplication (e.g., another agent application 110) running in theforeground process 150. The instance of the NLP component 116 of thedigital assistant application 108 on the client device 104 can initiateprocessing of the input audio signal without switching of the foregroundprocess 150 or the non-foreground process 152. The applications runningas the foreground process 150 and the non-foreground process 152 can bemaintained. For example, the NLP component 116 on the client device 104can receive and apply the natural language processing functions on theinput audio signal, without minimizing a graphical user interface of anapplication running as the foreground process 150. Alternatively, theNLP component 116 (and the digital assistant application 108 as a whole)can execute as one of the applications in the foreground process 150,when the input audio signal is received. Subsequent to the receipt ofthe input audio signal, the digital assistant application 108 cancontinue to execute as one of the applications in the foreground process150 of the client device 104.

The NLP component 116 can parse and convert the input audio signal intorecognized string by comparing the input signal against a stored,representative set of audio waveforms (e.g., in the data repository 128)and choosing the closest matches. The NLP component 116 can alsopartition or divide the input audio signal into one or more audiosegments of a time duration (e.g., 15 seconds to 2 minutes) to processeach segment. The set of audio waveforms can be stored in datarepository 128 or other database accessible to the data processingsystem 102. The representative waveforms are generated across a largeset of users, and then may be augmented with speech samples from theuser. After the audio signal is converted into recognized text, the NLPcomponent 116 matches the text to words that are associated, for examplevia training across users or through manual specification, with actionsthat the data processing system 102 can serve. The NLP component 116 candetermine that the input audio signal acquired from the microphone 146does not contain any recognizable strings. The NLP component 116 candetermine that the input audio signal contains silence (e.g., with amaximum amplitude of less than 0 dB) in determining that the input audiosignal does not contain any recognizable strings. Additionally, the NLPcomponent 116 can determine a signal-to-noise (SNR) of the input audiosignal. The NLP component 116 can compare the SNR of the input audiosignal to a threshold SNR (e.g., −20 dB). Responsive to thedetermination the SNR of the input audio signal is greater than thethreshold SNR, the NLP component 116 can determine that the input audiosignal does not contain any recognizable strings.

The data processing system 102 can receive image or video input signals,in addition to, or instead of, input audio signals. The NLP component116 can convert image or video input to text or digital files. The NLPcomponent 116 can process, analyze, or interpret image or video input toperform actions, generate requests, or select or identify datastructures. The data processing system 102 can process the image orvideo input signals using, for example, image interpretation techniques,computer vision, a machine-learning engine, or other techniques torecognize or interpret the image or video to convert the image or videoto a digital file. The one or more image interpretation techniques,computer vision techniques, or machine learning techniques can becollectively referred to as imaging techniques. The data processingsystem 102 (e.g., the NLP component 116) can be configured with theimaging techniques, in addition to, or instead of, audio processingtechniques.

From parsing the input audio signal, the NLP component 116 can determineor identify at least one request. The input audio signal can include,for example, a query, question, command, instructions, or otherstatement in a natural language. The request can correspond to at leastone trigger keyword identified from the recognized string converted fromthe input audio signal. The request can indicate an action to be taken.For example, the NLP component 116 can parse the input audio signal toidentify at least one request to leave home for the evening to attenddinner and a movie. The trigger keyword can include at least one word,phrase, root or partial word, or derivative indicating an action to betaken. For example, the trigger keyword “go” or “to go to” from theinput audio signal can indicate a request for transport. In thisexample, the input audio signal (or the identified request) does notdirectly express an intent for transport, however the trigger keywordindicates that transport is an ancillary action to at least one otheraction that is indicated by the request.

To identify the request, the NLP component 116 can apply a semanticprocessing technique to the input audio signal to identify the triggerkeyword corresponding to the request. The NLP component 116 can apply asemantic processing technique to the input audio signal to identify atrigger phrase that includes one or more trigger keywords, such as afirst trigger keyword and a second trigger keyword. For example, theinput audio signal can include the sentence “Find the nearest café.” TheNLP component 116 can determine that the input audio signal includes atrigger keyword “find.” The NLP component 116 can determine that therequest is to search for a location near the client device 104.

In addition to the request, the NLP component 116 can identify at leastone parameter defining the request. The parameter can define therequest, functioning as a supplement or a constraint on the actioncorresponding to the request to be taken. The parameter can furtherspecify the action to be-taken. The parameter can include a subset ofthe recognized strings (excluding the trigger keywords) converted fromthe input audio signal. The NLP component 116 can apply a semanticprocessing technique to the input audio signal to identify one or moredescriptor words related to the identified trigger keyword. From theexample “Find the nearest café,” the NLP component 116 may haveidentified the term “Find” as the trigger keyword. In conjunction, theNLP component 116 can identify “nearest” as a first parameter and “café”as a second parameter defining the request “find.”

Furthermore, the NLP component 116 can identify an applicationidentifier from the strings recognized from the input audio signal. Theapplication identifier can correspond to one of the agent applications110. To identify the application identifier, the NLP component 116 canperform named entity recognition algorithm to the strings recognizedfrom the input audio signal. In using the named entity recognitionalgorithm, the NLP component 116 can maintain a list of agentidentifiers for agent applications 110. The list can include agentidentifiers of agent applications 110 installed on the client device 104that received the input audio signal including the request. By applyingthe named-entity recognition algorithm, the NLP component 116 candetermine that the input audio signal includes the applicationidentifier corresponding to an agent application 110. For example, theNLP component 116 can determine that the input audio signal “Order carwith ride sharing service XYZ” includes with an explicit agentapplication 110 “ride sharing service XYZ.” Conversely, by applying thenamed entity recognition algorithm, the NLP component 116 can determinethat the input audio lacks any application identifier corresponding toany of the agent applications 110.

Based on the request, the NLP component 116 can determine whether therequest corresponds to a function of the digital assistant application108 or a function of the agent application 110. To determine, the NLPcomponent 116 can access a list of requests for functions of the digitalassistant application 108. The list of requests for the functions of thedigital assistant application 108 can be maintained on the datarepository 128. The list of requests can include sets of strings fortrigger keywords and requests corresponding to the requestspredetermined to be associated with functions of the digital assistantapplication 108. For example, the list can include “take”, “show”,“search for,” and “find,” among others. With the identification of therequest, the NLP component 116 can compare the request with the list ofrequests for functions of the digital assistant application 108.

The NLP component 116 can also use the regular expressions 130maintained on the data repository 128 to determine whether the requestcorresponds to the function of the digital assistant application 108.The regular expression 130 can define a pattern to match to determinewhether the keywords identified from the input audio signal referencesthe at least one function of the digital assistant application 108. Theregular expression 130 can also specify which keywords to use to carryout the command indicated in the input audio signal. For example, theregular expression 130 may be of the form {[request], [auxiliaryarguments]}. For the keywords of the input audio signal to be determinedto reference the functions of the digital assistant application 108, theregular expression 130 can specify that the one or more keywords includea request for the digital assistant application 108 and auxiliaryarguments. The regular expression 130 can specify a sequence for therequest and the referential keywords in the one or more keywordsidentified from the input audio signal.

Based on the comparison, the NLP component 116 can determine that therequest identified from the input audio signal matches one of the listof requests for functions of the digital assistant application 108. Inresponse to the determination, the NLP component 116 can determine thatthe request corresponds to one of the functions of the digital assistantapplication 108. For example, the NLP component 116 can parse the words“What is the weather?” from the input audio signal, and can identify theinput audio signal includes a request for weather. The list of requestsfor the functions of the digital assistant application 108 can specifythat the request for weather is one of the functions of the digitalassistant application 108. In this example, the NLP component 116 candetermine the match between the two requests, and can determine that therequest references one of the functions of the digital assistantapplication 108.

In response to the determination that the request corresponds to thefunction of the digital assistant application 108, the digital assistantapplication 108 can execute and fulfill the request identified from theparsing of the input audio signal. In addition, the digital assistantapplication 108 can execute the request in accordance with the parameterdefining the request. For example, the request may be to search for adefinition of a word (e.g., “abnegation”). The digital assistantapplication 108 can perform an internet search to retrieve thedefinition of the word. In fulfilling the request, the digital assistantapplication 108 can invoke the response selector component 122. Theresponse selector component 122 can select or identify responses phrasesusing the policies 134 or the response data 136 maintained on the datarepository 128. The policies 134 can be particular to a request, and canspecify the response data 136 for the request. The response selectorcomponent 122 can search the policies 134 for generating the outputusing the request type of the response in fulfilling the request. Oncethe policy 134 is identified, the response selector component 122 canselect the response phrase. The response phrase can include a set ofstrings, such as words or phrases. The digital assistant application 108can display the response phrase on the display 148 of the client device104. For example, the digital assistant application 108 can display acontent item including the response phrase on a graphical user interfaceof the digital assistant application 108 on the display 148 of theclient device 104.

With the identification of the response phrase, the digital assistantapplication 108 can invoke and the audio signal generator component 118.The instance of the digital assistant application 108 running on thedata processing system 102 or the client device 104 can execute theaudio signal generator component 118. Using the selected responsephrase, the audio signal generator component 118 can generate an outputaudio signal. Based on one or more words included in the responsephrase, the audio signal generator component 118 can generate the outputaudio signal. The audio signal generator component 118 can play theoutput audio signal on the speaker 144 of the client device 104.

Conversely, from the comparison, the NLP component 116 can determinethat the request parsed from the input audio signal does not match anyof the list of requests for function of the digital assistantapplication 108. In response to the determination, the NLP component 116can determine whether the request corresponds to one of the functions ofthe agent application 110. To determine, the NLP component 116 canaccess a list of requests for functions of the agent applications 110.The list of requests for functions can be for agent applications 110installed on the client device 104. The list of requests for thefunctions of the agent applications 110 can be maintained on the datarepository 128. The list of requests can include sets of strings fortrigger keywords or requests corresponding to the requests predeterminedto be associated with functions of the agent application 110. The NLPcomponent 116 can compare the request with the list of requests forfunctions of the agent application 110.

From the comparison, the NLP component 116 can determine that therequest identified from the input audio signal matches one of the listof requests for functions of the agent application 110. In response tothe determination, the NLP component 116 can determine that the requestcorresponds to one of the functions of the agent application 110. Forexample, the NLP component 116 can parse the words “Buy me laundrydetergent” from the input audio signal, and can identify the input audiosignal includes a purchase for detergent. The list of requests for thefunctions of the agent application 110 can specify that the request forweather is one of the functions of the agent application 110. In thisexample, the NLP component 116 can determine the match between the tworequests, and can determine that the request references one of thefunctions of the agent application 110, namely the one for suchpurchases. In addition, the NLP component 116 can determine that therequest does not correspond to a function of the digital assistantapplication 108, in response to determining that the input audio signalincludes the application identifier of the agent application 110.

On the other hand, the NLP component 116 can determine that the requestdoes not correspond to any function of any of the agent applications 110from the comparison. With the determination that the request does notcorrespond to the digital assistant application 108 or the agentapplication 110, the response selector component 122 can generate oridentify a response phrase indicating that the request does notcorrespond to any functionality available on the client device 014. Forexample, the response phrase can include “Sorry, I don't understand yourrequest.” The response phrase can be selected from the response data 136based on the determination. In addition, the audio signal generatorcomponent 118 can generate a corresponding output audio signal using theone or more words of the response phrase. The audio signal generatorcomponent 118 can play the output audio signal on the speaker 144 of theclient device 104.

The instance of the digital assistant application 108 running on thedata processing system 102 or the client device 104 can execute theaction handler component 120 to generate action data structures based onthe determination. The action handler component 120 can execute scriptsor programs based on input received from the NLP component 116. Theagent service 106 can provide the scripts or programs. The agent service106 can make the scripts or programs available to the data processingsystem 102 through an API. The action handler component 120 candetermine parameters or responses to input fields and can package thedata into an action data structure. The action data structure can beprovided to the agent application 110 through the API. The actionhandler component 120 can transmit the action data structure to theagent service 106 for fulfillment of the request identified from theinput audio signal parsed by the NLP component 116.

In response to the determination that the request corresponds to thefunction of the agent application 110, the action handler component 120can identify or select an action-inventory 140 from the data repository128 for the action corresponding to the request. At least oneaction-inventory 140 can be selected by the action handler component 120from the set of action-inventories 140 maintained on the data repository128. The action handler component 120 can use the request identifiedfrom the input audio signal to search the data repository 128 for theaction-inventory 140. The action handler component 120 can also use theone or more parameters identified from the input audio signal to searchthe data repository 128 for the action-inventory 140. The action handlercomponent 120 can traverse through the set of action-inventories 140maintained on the data repository 128. For each action-inventory 140,the action handler component 120 can identify the request identifier ofthe action-inventory 140.

The action handler component 120 can compare the request identified fromthe input audio signal with the request identifier of theaction-inventory 140. The comparison of the request identifier from theinput audio signal and the request identifier of the action-inventory140 can be in accordance with a semantic knowledge graph. The actionhandler component 120 can invoke the NLP component 116 to determinewhether the request is semantically related with the request identifierusing the semantic knowledge graph. The semantic knowledge graph caninclude a set of nodes and edges. Each node can correspond to one ormore words or a phrase. Each edge can define a semantic distance betweena pair of words indicated by the corresponding words on the nodes. Fromthe semantic knowledge graph, the NLP component 116 can identify thenode corresponding to the request, the node corresponding to the requestidentifier, and the semantic distance indicated in the pair of nodes.The NLP component 116 can compare the semantic distance to a thresholddistance. When the semantic distance is determined to not satisfy thethreshold distance (e.g., greater than), the NLP component 116 candetermine that the request does not match the request identifier of theaction-inventory 140. On the other hand, when the semantic distance isdetermined to satisfy the threshold distance (e.g., less than or equalto), the NLP component 116 can determine that the request does match therequest identifier of the action-inventory 140. From the comparison, theaction handler component 120 can determine that the request does notmatch the request identifier of the action-inventory 140. In response tothe determination, the action handler component 120 can identify thenext action-inventory 140 in the set maintained on the data repository128 and can repeat the comparison.

Conversely, from the comparison, the action handler component 120 candetermine that the request matches the request identifier of theaction-inventory 140. In response to the determination, the actionhandler component 120 can select the action-inventory 140 for the actioncorresponding to the request. As multiple requests may correspond to thesame action-inventory 140 as discussed above, the action handlercomponent 120 can select the action-inventory 140 that was or is to beselected for another request. The action handler component 120 can alsocompare the one or more parameters identified from the input audiosignal with the input variables of the action-inventory 140, prior toselection of the action-inventory 140. The action handler component 120can identify the input variables from the parameter mapping or theaddress template of the action-inventory 140. The action handlercomponent 120 can exclude the auxiliary parameters as indicated in theaction-inventory 140 in comparing the identified parameters with theinput variables of the action-inventory 140. The action handlercomponent 120 can determine that the identified parameters match theinput variables of the action-inventory 140 in accordance to the set ofpermitted values for each input variable. In response to thedetermination, the action handler component 120 can select theaction-inventory 140 for the action corresponding to the request definedby the one or more parameters. The action handler component 120 can alsohalt the traversal of the set of action-inventories 140 in the datarepository 128. Otherwise, the action handler component 120 candetermine that the identified parameters do not match the inputvariables of the action-inventory 140. The action handler component 120can identify another action-inventory 140 for the action correspondingto the same request, and can repeat the comparison. Upon comparing withall the action-inventories 140, the action handler component 120 candetermine that the identified parameters do not match the inputvariables in any of the action-inventories 140 of the agent application110. In response to the determination, the action handler component 120can select the preset action-inventory 140 for the agent application 110to respond to the request.

The action handler component 120 can also use the agent identifieridentified from the input audio signal to search the data repository 128for the action-inventory 140. Prior to searching using the request, theaction handler component 120 can identify a subset of theaction-inventories 140 with the application identifier matching theagent identifier. The agent identifier can correspond to one of theagent applications 110. Each action-inventory 140 of the identify subsetcan include the application identifier that is determined to match theagent identifier identified from the input audio signal. To identify thesubset, the action handler component 120 can compare the agentidentifier with the application identifier of each action-inventory 140.When the agent identifier is determined to match the applicationidentifier of the action-inventory 140, the action handler component 120can include the action-inventory 140 into the subset. Otherwise, whenthe agent identifier is determined to not match to the applicationidentifier of the action-inventory 140, the action handler component 120can exclude the action-inventory 140 from the subset. The action handlercomponent 120 can traverse through the identified subset ofaction-inventories 140 for the application identifier using the requestto select the action-inventory 140 for the action corresponding to therequest.

When the input audio signal is determined to lack an agent identifier,the action handler component 120 can select the action-inventory 140from the set maintained on the data repository 128 based on the request,the one or more parameters, and an agent usage history. The agent usagehistory can indicate usage statistics of the agent application 110 onthe client device 104 running the digital assistant application 108 fromwhich the input audio signal is received. The agent usage history canalso indicate functions of the agent application 110 invoked on theclient device 104. The agent usage history can be limited to a definedtime window prior to the request identified from the input audio signaldetected on the client device 104. The action handler component 120 canidentify a subset of action-inventories 140 with request identifiersmatching the request and the one or more parameters. The subset caninclude the action-inventories 140 with different applicationidentifiers corresponding to multiple agent applications 110. The actionhandler component 120 can use the agent usage history for the clientdevice 104 to select the action-inventory 140 from the subset. Theaction handler component 120 can identify at least one agent identifierfrom the agent usage history. The action handler component 120 cancompare the agent identifier with application identifier of eachaction-inventory 140 in the identified subset. The action handlercomponent 120 can determine that application identifier of theaction-inventory 140 matches the agent identifier from the agent usagehistory from the comparison. In response to the determination, theaction handler component 120 can select the action-inventory 140 for theaction to be executed by the agent application 110 in accordance withthe parameter. Conversely, the action handler component 120 candetermine that the application identifier of the action-inventory 140does not match the agent identifier from the agent usage history fromthe comparison. In response to the determination, the action handlercomponent 120 can identify another action-inventory 140 and can repeatthe comparison using the agent identifier.

With the identification of the action-inventory 140, the action handlercomponent 120 can validate the one or more parameters identified fromthe input audio signal against the address template of theaction-inventory 140. The validation by the action handler component 120may be to check whether there are prerequisite parameters as specifiedby the action-inventory 140 to carry out the action corresponding to therequest. For example, for a ridesharing request, the action handlercomponent 120 can check whether there is a parameter corresponding tothe destination as parsed from the input audio signal. The actionhandler component 120 can use the parameter mapping for the addresstemplate of the action-inventory 140 in validating the parameters. Theaction handler component 120 can identify the correspondences betweenparameters and input variables defined in the mapping for theaction-inventory 140. The action handler component 120 can identify asubset of correspondences for input variables not specified as auxiliaryby the mapping of the action-inventory 140 for the address template.

From each input variable not indicated as auxiliary, the action handlercomponent 120 can determine whether at least one of the parameterscorresponds to the input variable as specified by the mapping. Thedetermination of the correspondence can be performed using semanticanalysis algorithms as provided by the NLP component 116 (e.g., semanticknowledge graph). For each input variable, the action handler component120 can invoke the NLP component 116 to determine whether the inputvariable corresponds to any of the parameters, or vice-versa. Inresponse to determination that all the input variables corresponds to atleast one parameter, the action handler component 120 can determine thatthe parameters are successfully validated. The action handler component120 can also continue to use the address template of theaction-inventory 140 to generate an address to fulfill the actioncorresponding to the request.

On the other hand, in response to the determination that at least oneinput variable (not indicated as auxiliary) does not correspond to anyparameter, the action handler component 120 can determine that theparameters are not successfully validated. The action handler component120 can cease or terminate further processing of the request and theparameters (e.g., generation of an address using the address template ofthe action-inventory 140). The action handler component 120 can detector determine an error in validating the one or more parametersidentified from the input audio signal. The digital assistantapplication 108 can present an indication (e.g., using a visual contentitem or audio) that the request is invalid or unsuccessful. The actionhandler component 120 can provide an indication of the error to theagent service 106 or an administrator for the agent application 110associated with the action-inventory 140.

Upon identifying the action-inventory 140, the action handler component120 can determine whether the client device 104 is authenticated withthe agent application 110 associated with the action-inventory 140. Theaction handler component 120 can identify the agent application 110associated with the action-inventory 140. Once identified, the actionhandler component 120 can check an authentication status of the clientdevice 104 with the agent application 110. The checking of theauthentication status can be performed using an account identifier ofthe client device 104 or the digital assistant application 108. Theaction handler component 120 can send a request for the authenticationstatus to the agent service 106 managing resources of the agentapplication 110. The request can include the account identifier of theclient device 104 or of the digital assistant application 108. The agentservice 106 can provide a response to the action handler component 120indicating whether the client device 104 is authenticated with the agentapplication 110. When the response indicates that the client device 104is authenticated, the action handler component 120 can determine thatthe client device 104 is authenticated with the agent application 110.The action handler component 120 can also continue processing therequest. On the other hand, when the response indicates that the clientdevice 104 is not authenticated, the action handler component 120 candetermine that the client device 104 is not authenticated with the agentapplication 110. The action handler component 120 can cease or terminatefurther processing of the request (e.g., generation of an address usingthe address template of the action-inventory 140). The digital assistantapplication 108 can also present an indication to authenticate with theagent application 110 to carry out the action corresponding to therequest. For example, the digital assistant application 108 can render aprompt for logging into the agent application 110 on the display 148 ofthe client device 104. The prompt can include a field for an accountidentifier of the user and the passcode.

In addition, the action handler component 120 can also determine whetherthe agent application 110 associated with the action-inventory 140 isinstalled on the client device 104. The action handler component 120 canidentify the agent application 110 associated with the action-inventory140. Once identified, the action handler component 120 can access theclient device 104 to determine whether the agent application 110 isinstalled on the client device 104. For example, the action handlercomponent 120 can access a list of installed applications on the clientdevice 104 to determine whether the agent application 110 is installed.The action handler component 120 can check the application identifier orthe agent identifier to the list. In response to the determination thatthe agent application 110 is installed, the action handler component 120can continue to process the request. On the other hand, in response tothe determination that the agent application 110 is not installed, theaction handler component 120 can terminate processing of the request(e.g., generation of an address using the address template of theaction-inventory 140). The digital assistant application 108 can alsopresent an indication to install the agent application 110 to carry outthe action corresponding to the request. For example, the digitalassistant application 108 can render a prompt indicating that thecorresponding agent application 110 is not installed on the display 148of the client device 104. The prompt can also include a link to installthe agent application 110.

The action-inventory 140 selected by the action handler component 120can correspond to the agent application 110 not running as one ofapplications in the foreground process 150 or the non-foreground process152. For example, the action-inventory 140 can correspond to the agentapplication 110 installed on the client device 104, but not running onthe client device 104. The action-inventory 140 selected by the actionhandler component 120 can correspond to the agent application 110running in the non-foreground process 152. For example, anotherapplication (e.g., another agent application 110 or the digitalassistant application 108) can be running in an application of theforeground process 150. The application in the foreground process 150can have a graphical user interface rendered on at least a portion ofthe display 148 of the client device 104. In contrast, the applicationrunning in the non-foreground process 152 can lack a graphical userinterface rendered on the display 148 of the client device 104, and canexecute routines (e.g., the action). In addition, the action-inventory140 selected by the action handler component 120 can correspond to theagent application 110 running in the foreground process 150. Forexample, the agent application 110 corresponding to the action-inventory140 can have a graphical user interface currently rendered on thedisplay 148 of the client device 104.

The action handler component 120 can generate an address in accordancewith the address template of the action-inventory 140. The actionhandler component 120 can identify the address template of theaction-inventory 140 selected from the set maintained on the datarepository 128. As described above, the address template of theaction-inventory 140 can include: a first portion referencing the agentapplication 110; and a second portion referencing the action to beperformed and the one or more input variable used to execute the action.For example, the address template can be a URI template. The firstportion can include a scheme referencing the agent application 110 or ahostname referencing the agent service 106 or the agent application 110.The second portion can include a pathname referencing the action and oneor more query strings corresponding to one or more input variable sinthe URI. For example, the address template of the action-inventory 140can be “https://ex_personalmetrics. example.com/checksteps{?username}”for a request to check a number of steps taken. The first portion cancorrespond to “https://ex_personalmetrics.example.com/” and the secondportion can correspond to “checksteps{?username}.”

The address generated in accordance with the address template caninclude a first substring and a second substring. The first substring ofthe generated address can correspond to the first portion of the addresstemplate. The generated address can be a portion of the URI, and thefirst substring can include the scheme referencing the agent application110 or the hostname referencing the agent service 106 or the agentapplication 110. The scheme and the hostname can be taken by the actionhandler component 120 from the first portion of the address template.The second substring of the generated address can correspond to thesecond portion of the second template. The generated address can also bea portion of the URI, and the second substring can include the pathnamereferencing the action to be executed by the agent application 110 andquery strings including the parameters identified from the input audiosignal. For example, the address generated in accordance with theaddress template can be“https://ex_personalmetrics.example.com/checksteps?username=example_user_id.”The first substring of the address can include“https://ex_personalmetrics.example.com” and the second substring of theaddress can include “checksteps?username=example_user_id.”

In generating the address, the action handler component 120 can use orset the first portion of the address template as a first substring ofthe address to reference the agent service 106 or the agent application110 associated with the agent service 106. The action handler component120 can use the second portion of the address template as a secondsubstring of the address to correspond to the action and the parametersused to execute the action. The action handler component 120 canpopulate the input variables of the second portion of the addresstemplate with the one or more parameters identified from the input audiosignal.

The action handler component 120 can populate in accordance with theparameter mapping of the action-inventory 140 defined for the addresstemplate. As discussed above, the parameter mapping can define acorrespondence between the input variables of the second portion andwords to be identified from parsing input audio signals. The actionhandler component 120 can use the parameters as the words identifiedfrom the input audio signal to insert into the second portion of theaddress template in populating the input variables. The population or ofthe second portion of the address template can be in accordance withexpression expansion in URI templates. For each input variable specifiedin the address template, the action handler component 120 can identifythe corresponding parameters as specified by the mapping of theaction-inventory 140. With the identification, the action handlercomponent 120 can insert, replace, or set the query string with a nameof the input variable and the identified parameter. For example, theinput variable may be “{?username}” in the address template and theparameter identified may be “example_user_id”. In this example, theaction handler component 120 can replace with“?username=example_user_id” in the second substring of the address inaccordance with expression expansion for URI templates.

In populating the input variables of the address template, the actionhandler component 120 can determine whether the input variable is anauxiliary as specified in the mapping for the address template of theaction-inventory 140. In response to the determination that the inputvariable is auxiliary, the action handler component 120 can alsodetermine whether there is an identified parameter that corresponds tothe auxiliary input variable. When there is determined to be noparameters that correspond to the auxiliary input variable, the actionhandler component 120 can omit or remove the in auxiliary input variablefrom the address. The generated address can thus lack one or moreparameters corresponding to auxiliary input variables in the addresstemplate. Otherwise, when there is determined to be a parameter thatcorresponds to the auxiliary input variable, the action handlercomponent 120 can insert or populate the auxiliary input variable withthe parameter. Conversely, in response to the determination that theinput variable is not auxiliary, the action handler component 120 canidentify a parameter from the identified parameters to include into theinput variable.

With the generation of the address in accordance with the addresstemplate, the action handler component 120 can validate the address. Thevalidation of the address by the action handler component 120 may be tocheck whether the address is well-formed. To validate, the actionhandler component 120 can check the address against a regular expression130 for addresses (e.g., URIs or URLs). The regular expression 130 foraddresses can include, for example, schema, hostnames, pathnames, andquery strings separated by delimiters for valid addresses. The actionhandler component 120 can compare the address against the regularexpression 130 to determine whether the address matches the pattern foraddresses as specified by the regular expression 130. In response to thedetermination that the address matches, the action handler component 120can determine that the generated address is successfully validated.

Conversely, in response to the determination that the address does notmatch, the action handler component 120 can determine that the generatedaddress is not successfully validated. Based on the determination, theaction handler component 120 can also detect an error in validating thegenerated address. The error can indicate that the address is notwell-formed. Furthermore, the action handler component 120 can cease orterminate further processing of the address (e.g., generating an actiondata structure). The action handler component 120 can provide anindication of the error to the agent service 106 or an administrator forthe agent application 110 associated with the action-inventory 140.

The action handler component 120 can package or generate an action datastructure using the address for executing the action. The generation ofthe action data structure can be in accordance with an applicationprogramming interface (API). For example, the API can be specified by anoperating system running on the client device 104, and can be used byboth the digital assistant application 108 and the agent application110. The action data structure can be passed between the digitalassistant application 108 and the agent application 110 via the API. Thegeneration of the action data structure can be in accordance with theHypertext Transfer Protocol (HTTP). For example, the action datastructure generated by the action handler component 120 can be an HTTPrequest (e.g., GET or POST functions). The action data structure caninclude at least one header and at least one body. The header caninclude a device modality (e.g., a smartphone, smart speaker, tablet,laptop, and desktop) of the client device 104 executing the digitalassistant application 108 and the agent application 110. The header caninclude a source address set to the client device 104. The header caninclude the generated address set a destination address. The body of theaction data structure can include other information related to therequest identified from parsing the input audio signal. For example, thebody can include an identifier referencing the digital assistantapplication 108 or the client device 104 running the digital assistantapplication 108.

The instance of the digital assistant application 108 on the dataprocessing system 102 or the client device 104 can execute the agentinterface component 126 to provide the action data structure to theagent application 110. With the generation of the action data structure,the agent interface component 126 can provide or direct the action datato the agent application 110. The agent interface component 126 cantransmit the action data structure over the network 114 to the agentservice 106 managing resources for the agent application 110 (e.g., asan HTTP request). For example, an HTTP request corresponding to theaction data structure can be transmitted by the agent interfacecomponent 126 over the network 114. The agent interface component 126can invoke the agent application 110 using the action data structure(e.g., via the API). For example, the agent interface component 126 canmake a function call to invoke the agent application 110 in accordanceto an API and facilitated by the operating system of the client device104. In invoking, the agent interface component 126 can pass the actiondata structure to the agent application 110. In invoking, the agentinterface component 126 can pass the action data structure to the agentapplication 110.

The data processing system 102, the client device 104, or the agentservice 106 can execute an instance of the agent application 110. As thedestination address of the data structure can reference the agentapplication 110 or the agent service 106, the agent application 110 canreceive the action data structure from the agent interface component126. For example, the action data structure may have been sent via thenetwork 114, and can the destination address can include the hostnamereferencing the agent application 110 or the agent service 106. Sincethe destination address of the action data structure references theagent application 110 or the agent service 106, the action datastructure can be routed to the agent application 110 or the agentservice 106 by the network 114. In another example, the destinationaddress of the action data structure can be a deep link with a schemereferencing the agent application 110. By invoking the destinationaddress, the action data structure can be directed by the client device104 or the network 114 to the agent application 110 referenced by thescheme.

Upon passing of the action data structure, the agent application 110 canparse the action data structure to identify the address. Theidentification of the address can be from the destination address headerof the action data structure. The agent application 110 can parse theaddress to identify the first substring of the address referencing theagent application 110 itself or the agent service 106 managing resourcesfor the agent application 110. The agent application 110 can parse theaddress the second substring of the address. The agent application 110can further parser the second substring of the address to identify theaction and the one or more parameters used to perform the action. Theagent application 110 can parse the pathname of the URI to identify theaction and parse the one or more query strings to identify the one ormore parameters used to execute the action. For example, the agentapplication 110 can parse the address“https://ex_personalmetrics.example.com/checksteps?username=example_user_id”to identify the second substring “checksteps?username=example_user_id.”The agent application 110 can further identify “checksteps” as a requestto get a number of steps measured and the “Example_user_id” as the nameof the user whose steps were measured. With the identification, theagent application 110 can perform, carry out, or execute the action inaccordance with the one or more parameters. Using the previous example,the agent application 110 can perform the series of processes androutines to retrieve the number of steps taken by the user of the agentapplication 110 with the account identifier “example_user_id.” The agentapplication 110 can provide the output of the execution of the action tothe agent interface component 126.

The agent application 110 can also generate an output to indicatewhether the execution of the action is successful or a failure to sendto the digital assistant application 108. In executing the agent, theagent application 110 can fail in completing the action or terminateshort of completion. For example, while processing the request fornumber of steps, the agent service 106 can determine that theinformation on the number of steps taken by the corresponding usercannot be retrieved. Based on the determination, the agent application110 can create the output indicating the failure. In response to thefailure, the agent application 110 can generate the output indicatingfailure. Conversely, the agent application 110 can complete theexecution of the action. In response to the completion, the agentapplication 110 can generate the output indicating success. The agentapplication 110 can provide the output of the execution of the action tothe agent interface component 126.

In conjunction with the passing of the action data structure, the agentinterface component 126 can control whether the agent application 110 isto be run as the non-foreground process 152 or the foreground process150. The setting or controlling of the foreground process 150 or thenon-foreground process 152 can be based on the interface mode indicatorof the action-inventory 140 used to generate the action data structure.The setting of the foreground process 150 and the non-foreground process152 by the agent interface component 126 can be facilitated by thatoperating system running on the client device 104. As discussed above,the agent application 110 can be running as one the applications in theforeground process 150 or the non-foreground process 152, or neither theforeground process 150 nor the non-foreground process 152. With thepassing of the action data structure, the agent interface component 126can control whether the agent application 110 is to be set from thenon-foreground process 152 to the foreground process 150.

Furthermore, the agent interface component 126 can identify whichapplications are running in the foreground process 150 and as thenon-foreground process 152, such as the digital assistant application108 and the agent applications 110 installed on the client device 104.For example, the agent interface component 126 can access the operatingsystem of the client device 104 to identify applications running as theforeground process 150 and applications running in the non-foregroundprocess 152. The agent interface component 126 can identify whether theagent application 110 (or other applications on the client device 104)is one of the foreground process 150 or the non-foreground process 152.The agent interface component 126 can identify the agent application 110as running as one of the applications in the foreground process 150. Theagent interface component 126 can identify the agent application 110 asrunning as one of the applications in the non-foreground process 152.The agent interface component 126 can identify the agent application 110as running as one of the applications neither in the foreground process150 nor the non-foreground process 152. In response to determining thatthe agent application 110 is running neither as the foreground process150 nor the non-foreground process 152, the agent interface component126 can cause the client device 104 to initiate execution of the agentapplication 110.

From the selected action-inventory 140, the agent interface component126 can identify the interface mode indicator. The interface modeindicator can specify the user interface component 142 of the agentapplication 110 is to be rendered on the display 148 of the clientdevice 104 in executing the action corresponding to the action-inventory140. When the interface mode indicator specifies that no user interfacecomponent 142 is to be rendered, the agent interface component 126 canset the agent application 110 as the foreground process 150. When theagent application 110 is identified as not executing on the clientdevice 104, the agent interface component 126 can launch the agentapplication 110 in the foreground process 150. When the agentapplication 110 is identified as running in the non-foreground process152, the agent interface component 126 can remove the applicationoriginally in the foreground process 150 (e.g., another agentapplication 110 or the digital assistant application 108) and set to thenon-foreground process 152. In addition, the agent handler component 126can set the agent application 110 from the non-foreground process 152 tothe foreground process 150. When the agent application 110 is identifiedas already in the foreground process 150, the agent interface component126 can maintain the agent application 110 in the foreground process150.

When the interface mode indicator specifies that a user interfacecomponent 142 is to be rendered, the agent interface component 126 canapply at least one authorization policy of the agent application 110.The authorization policy can specify for which applications the outputof the agent application 110 is restricted or permitted to be presentedwith. For example, the authorization policy for one personal fitnessapplication can specify that the output is to be restricted from beingpresented with another personal fitness application. The authorizationpolicy can include a list of application (also referred herein ablacklist) for which the output of the agent application 110 isrestricted from concurrent presentation. The authorization policy canalso include a list of application (also referred herein as a whitelist)for which the output of the agent application 110 is permitted forconcurrent presentation. Each list can include agent identifiers (e.g.,application file names) corresponding to the included applications. Theauthorization policy can be specific to an output type of the agentapplication 110. The output type can depend on the request identifiedfrom parsing the input audio signal. For example, the authorizationpolicy can restrict displays of a number of steps while another personalfitness application is in the foreground but can permit displays ofaccount credential information.

The determination of whether to apply the authorization policy can bebased on whether the agent application 110 is running in the foregroundprocess 150 or the non-foreground process 152. When the agentapplication 110 is identified as in the foreground process 150, theagent interface component 126 can determine not to apply theauthorization policy. The agent interface component 126 can also permitthe user interface component 142 of the agent application 110 with theoutput to be rendered in the display 148 of the client device 104. Whenanother application besides agent application 110 is identified asrunning in the foreground process 150, the agent interface component 126can determine to apply the authorization policy. In this manner, theagent application 110 can remain as part of the non-foreground process152 or not executing on the client device 104. In determining whether toapply, the agent interface component 126 can also identify theauthorization policy based on the request parsed from the input audiosignal. The agent interface component 126 can compare the identifiedrequest with the output type for the authorization policy. Upondetermining a match, the agent interface component 126 can determine toapply the authorization policy specified for the corresponding outputtype.

In accordance with the authorization policy, the agent interfacecomponent 126 can determine whether the output of the agent application110 is authorized to be presented with the graphical user interfacecomponent of the application in the foreground process 150. The agentinterface component 126 can identify the application in the foregroundprocess 150. The agent interface component 126 can identify the agentidentifier of the application in the foreground process 150. The agentinterface component 126 can compare the application with the lists ofapplication specified in the authorization policy of the agentapplication 110. In comparing, the agent interface component 126 can usethe identified agent identifier to search both the whitelist and theblacklist of the authorization policy for the agent application 110. Ifthe application in the foreground process 150 matches one of theapplications in the whitelist, the agent interface component 126 candetermine to permit the output of the agent application 110 to bepresented with the application. On the other hand, if the application inthe foreground process 150 matches one of the applications in theblacklist, the agent interface component 126 can determine to restrictthe output from being presented with the application.

When the output of the agent application 110 is determined to bepermitted, the agent interface component 126 can identify the userinterface component 142 of the agent application 110. To identify theuser interface component 142, the agent interface component 126 can usethe address generated in accordance with the address template of theaction-inventory 140. For example, the address generated in accordancewith the address template can reference both the action to be executedby the agent application 110 and the user interface component 142 to berendered in carrying out the action. The address generated in accordancewith the address template can reference the agent application 110 or theagent service 106 managing resources for the agent application 110. Theagent interface component 126 can identify a separate address oridentifier for the user interface component 142 from theaction-inventory 140. The address can reference the user interfacecomponent 142 maintained by the agent service 106. The address andidentifier can reference the user interface component 142 maintained onthe data repository 128. Using the separate address or identifier, theagent interface component 126 can identify the user interface component142 to be rendered in conjunction with the execution of the action bythe agent application 110.

Upon identifying, the agent interface component 126 can access orretrieve the user interface component 142. Using the address generatedaccording to the address template of the action-inventory 140, the agentinterface component 126 can retrieve the user interface component 142.The agent interface component 126 can send a request for the userinterface component 142 to the agent service 106 including the address.As the address references the agent service 106, the request can bedirected to the agent service 106 handling resources for the agentapplication 110. The agent service 106 in turn can provide a responsewith the referenced user interface component 142 to the agent interfacecomponent 126. Using the address included in the action-inventory 140,the agent interface component 126 can retrieve the user interfacecomponent 142. The address included in the action-inventory 140 can beseparate from the address generated using the address template, and canreference the agent service 106 or the data repository 128. The agentinterface component 126 can send a request for the user interfacecomponent 142 including the address. When the address references theagent service 106, the request can be directed to the agent service 106handling resources for the agent application 110. When the addressreferences the data repository 128, the request can be directed to thedata repository 128. The agent service 106 or the data repository 128 inturn can provide a response with the referenced user interface component142 to the agent interface component 126. Using the identifier includedin the action-inventory 140, the agent interface component 126 canretrieve the user interface component 142 from the data repository 128.The identifier can correspond to an index of the user interfacecomponent 142 maintained on the data repository 128. The agent interfacecomponent 126 can search the data repository 128 using the identifier tofind the user interface component 142. Once identified, the agentinterface component 126 can retrieve the user interface component 142from the data repository 128.

Prior to rendering the user interface component 142, the agent interfacecomponent 126 can also apply an authorization policy of the applicationin the foreground process 150. The authorization policy can specifywhich applications the graphical user interface component of the agentin the foreground process 150 is restricted or permitted to be presentedwith. For example, the authorization policy for one banking applicationcan specify that the output is to be restricted from being presentedwith another banking application. The authorization policy can include alist of application (also referred herein a blacklist) for which thegraphical user interface of the application in the foreground process150 is restricted from concurrent presentation. The authorization policycan also include a list of application (also referred herein as awhitelist) for which the graphical user interface of the application inthe foreground process 150 is permitted for concurrent presentation.Each list can include agent identifiers (e.g., application file names)corresponding to the included applications.

In accordance with the authorization policy, the agent interfacecomponent 126 can determine whether the graphical user interfacecomponent of the application in the foreground process 150 is authorizedto be presented with the output of the agent application 110. The agentinterface component 126 can identify the agent application 110 executingthe action. The agent interface component 126 can identify the agentidentifier of the agent application 110. The agent interface component126 can compare the application with the lists of application specifiedin the authorization policy of the application in the foreground process150. In comparing, the agent interface component 126 can use theidentified agent identifier to search both the whitelist and theblacklist of the authorization policy for the application in theforeground process 150. If the agent application 110 matches one of theapplications in the whitelist, the agent interface component 126 candetermine to permit concurrent presentation with the graphical userinterface of the application in the foreground 150. On the other hand,if the agent application 110 matches one of the application in theblacklist, the agent interface component 126 can determine to restrictthe concurrent presentation.

With the identification of the user interface component 142, the agentinterface component 126 can render the user interface component 142 ofthe agent application 110 in the display 148 of the client device 104.With the determination that concurrent presentation is permitted, theuser interface component 142 of the agent application 110 can berendered on the display 148 concurrent with the graphical user interfaceof the application running in the foreground process 150. The agentinterface component 126 can render the user interface component 142 asan overlay superimposed on the graphical user interface of theapplication in the foreground process 150. The agent interface component126 can also include the user interface component 142 as a portion ofthe graphical user interface of the application in the foregroundprocess 150. For example, the application running as the foregroundprocess 150 can be the digital assistant application 108, and can have agraphical user interface including a dialog with the user operating thedigital assistant application 108 on the client device 104. The agentinterface component 126 can insert the user interface component 142 inthe dialog of the graphical user interface of the digital assistantapplication 108.

The agent interface component 126 can add or insert information into theuser interface component 142 rendered on the display 148 of the clientdevice 104. The agent interface component 126 can add, insert, orinclude the words or the request from the input audio signal into acorresponding interface element of the user interface component 142. Thewords or the request can be identified by the NLP component 116 fromparsing the input audio signal. For example, the agent interfacecomponent 126 can incorporate the words with the request onto a textboxof the user interface component 142. The agent interface component 126can retrieve, receive, or identify the output generated by the agentapplication 110. The agent interface component 126 can withhold therendering of the user interface component 142 and can wait for theoutput from the agent application 110. Upon receipt of the output fromthe agent application 110, the agent interface component 126 can add,insert, or include the output into a corresponding interface element ofthe user interface component 142. For example, the agent interfacecomponent 126 can receive an output indicating the number of steps takenby the user of the agent application 110 installed on the client device104. The agent interface component 126 can insert the number of stepsinto another textbox of the user interface component 142. With thereceipt and insertion of the output, the agent interface component 126can render the user interface component 142 on the display 148.

As the user interface component 142 is rendered on the display 148 alongwith the graphical user interface of the application in the foregroundprocess 150, the agent interface component 126 can monitor for userinteraction events with the user interface component 142. The userinteraction events can include, for example, hover-overs, clicks,scrolling, flicking, keypresses, and touch screens, among others. Upondetecting a user interaction event on the user interface component 142,the agent interface component 126 can process the user interaction eventto update the user interface component 142. The agent interfacecomponent 126 can relay the detected user interaction event to the agentapplication 110. The agent application 110 can process the userinteraction event (e.g., using an event handler) and can generateanother output in response to the user interaction event. The agentapplication 110 can provide the output to the agent interface component126. Using the output received from the agent application 110, the agentinterface component 126 can update the user interface component 142.

In this manner, the agent interface component 126 can maintain theapplication originally in the foreground process 150, while adding auser interface component 142 from the agent application 110 for displayas an overlay. The agent interface component 126 can have both theoriginal application as well as the agent application 110 both asapplications in the foreground process 150. The agent interfacecomponent 126 can also maintain visual components from both applicationsrendered on the display 148 of the client device 104, thereby reducinguser of the client device 104 to perform context switching. By keepingboth, the agent interface component 459 can also reduce computingresources incurred from switching the rendering and between theforeground process 150 and the non-foreground process 152.

Conversely, when the output of the agent application 110 is determinedto be restricted, the agent interface component 126 can set the agentapplication 110 as the foreground process 150. When the agentapplication 110 is identified as not running on the client device 104,the agent interface component 126 can invoke and launch the agentapplication 110 (e.g., via a the operating system of the client device104). The agent interface component 126 can move the applicationoriginally running as the foreground process 150 and can set theapplication as running as the non-foreground process 152. In switchingthe foreground process 150 and the non-foreground process 152, the agentinterface component 126 can remove the graphical user interfacecomponent of the application originally in the foreground process 150from being rendered on the display 148. In addition, the agent interfacecomponent 126 can invoke the agent application 110 using the action datastructure generated by the action handler component 120. Instead ofrendering the user interface component 142, the agent interfacecomponent 126 can render the graphical user interface of the agentapplication 110 on the display 148 of the client device 104.

Running as the foreground process 150, the agent application 110 candisplay the output of the action indicated in the address of the actiondata structure on the graphical user interface rendered in the display148. The agent application 110 can monitor for user interaction eventswith the graphical user interface. Upon detecting a user interactionevent on the user interface component 142, the agent application 110 canprocess the user interaction event (e.g., using an event handler) andcan generate another output in response to the user interaction event.The agent application 110 can update the graphical user interfacerendered in the display 148 of the client device 104 using the generatedoutput.

By controlling the switching between the foreground process 150 and thenon-foreground process 152, the user involvement to search for the agentapplication 110 may be eliminated, thereby improving the HCI with theapplications on the client device 104. In addition, the digitalassistant application 108 can regulate and reduce consumption ofcomputing resources on the client device 104 from the switching.

FIG. 2 depicts a sequence diagram of an example data flow 200 to rendingvisual components on applications in the system 100 illustrated inFIG. 1. The data flow 200 can be implemented or performed by the system100 described above in conjunction with FIG. 1 or system 500 detailedbelow in conjunction with FIG. 5. The data flow 200 an includecommunications in the form of packets (e.g., HTTP messages) among themicrophone 150, the client device 104, the data processing system 102,the agent service 106 via the network 114, and the display 148.

A local instance of the digital assistant application 108 running on theclient device 104 can receive audio data 205 (e.g., the input audiosignal) from a microphone 146 communicatively coupled with the clientdevice 104. The digital assistant application 108 can execute on theclient device 104 in the non-foreground process 152, without any visualcomponent rendered on the display 148. The client device 104 can haveanother application in the foreground process 150, with a graphical userinterface rendered on the display 148. The digital assistant application108 on the client device 104 can perform initial processing (e.g.,automated speech recognition) on the audio data 205 to identify one ormore words from the audio data 205. The digital assistant application108 can provide the one or more recognized words from the audio data 205as an input 210 to a remote instance of the digital assistantapplication 108 running on the data processing system 102. The NLPcomponent 116 on the data processing system 102 in turn can furtherprocess the one or more words of the input 210 to identify a request andone or more parameters. The request can indicate an action to beperformed by the agent application 110 in accordance with the one ormore parameters.

The action handler component 120 on the data processing system 102 canidentify an action-inventory 140 from the data repository 128 using therequest and the one or more parameters. The agent application 110associated with the identified action-inventory 140 can be not executingon the client device 104 or can be running as one of the applications ofthe non-foreground process 152. The action handler component 120 cangenerate an address in accordance with an address template of theidentified action-inventory 140. The address can include a firstsubstring (e.g., a scheme or hostname) referencing the agent applicationthat is to carry out the action. The address can additionally include asecond string corresponding to the action to be executed and the one ormore parameters in accordance to which the action is to be executed. Theaction handler component 120 can package the address into an action datastructure to provide as an input 215 to the agent service 106 for theagent application 110.

Upon receipt of the input 215, the agent service 106 for the agentapplication 110 can parse the action data structure to identify thefirst substring and the second substring. As the input is processed, theclient device 104 can maintain applications in running as the foregroundprocess 150 and as the non-foreground process 152. The agent application110 executing on the agent service 106 can further parse the second substring to identify the action and the one or more parameters. With theidentification, the agent application 110 can execute the action inaccordance with the parameters. In executing the action, the agentapplication 110 can generate an output 220 to provide to the clientdevice 104 via the data processing system 102. The agent service 106 canprovide the output 220 to the data processing system 102. The digitalassistant application 108 on the data processing system 102 can send theoutput 220 as an output 225 to the client device 104.

In conjunction, the agent interface component 126 can determine that theaction-inventory 140 specifies that a user interface component 142 is tobe rendered in carrying out the action. In response to thedetermination, the agent interface component 126 can identify a userinterface component 235 (e.g., using the address generated using theaddress template of the action-inventory 140) from the set of userinterface components 142. The agent interface component 126 can providethe user interface component 235 to the client device 104. Using theuser interface component 235, the client device 104 can displayrendering data 240 for the display 148 of the client device 104. Therendering data 240 can include the user interface component 235 as anoverlay superimposed on the graphical user interface of the applicationin the foreground process 150. The client device 104 can maintain theapplications in the foreground process 150 and the non-foregroundprocess 152 prior to the receipt of the audio data 205 from themicrophone 146.

FIG. 3 illustrates a use case diagram of an example client device 104displaying input messages and providing user interface components in thesystem 100 illustrated in FIG. 1. The client device 104 can have anapplication running as the foreground process 150 and a local instanceof the digital assistant application 108 running as the non-foregroundprocess 152. The application running as the foreground process 150 canhave a graphical user interface 305 rendered within the display 148 ofthe client device 104. As depicted, the graphical user interface 305 canbe for a web browser application running as the foreground process 150.In this context, the NLP component 116 of the digital assistantapplication 108 running on the client device 104 can receive an inputaudio signal via the microphone 146 of the client device 104. The NLPcomponent 116 can apply automated speech recognition to identify one ormore words 310 from the input audio signal. For example, the NLPcomponent 116 can identify the words 310 “How many steps have I takentoday?” from the input audio signal.

The NLP component 116 on the client device 104 or the data processingsystem 102 can perform further processing on the words 310. By furtherprocessing, the NLP component 116 can identify the request from thewords 310 recognized from the input audio signal. In the exampledepicted, the NLP component 116 can identify the request as a fetchrequest for a number of steps taken by a user operating or otherwiseassociated with the client device 104. Using the identified request, theaction handler component 120 can identify an agent application 110capable of performing the request. The action handler component 120 canalso select an action-inventory 140 from the data repository 128. Theaction-inventory 140 can be for the action corresponding to the requestto be executed by the agent application 110. Using the action-inventory140, the action handler component 120 can invoke the agent application110 to carry out the action corresponding to the request.

In conjunction, the agent interface component 126 can identify that auser interface component 142 is to be displayed in carrying out theaction of the action-inventory 140. The action-inventory 140 can specifywhether a user interface component 142 is to be displayed, and canidentify which user interface component 142 is to be presented. Inresponse to the identification, the agent interface component 126 candetermine whether concurrent presentation is permitted with thegraphical user interface component 305 of the foreground application.The determination can be in accordance with an authorization policy forthe agent application 110. The authorization policy for the agentapplication 110 can specify which applications are allowed to beconcurrently presented with the user interface component 142 of theagent application 110. In the example depicted, the agent interfacecomponent 126 can determine that concurrent presentation is permitted.

In response to the determination, the agent interface component 126 canidentify the user interface component 142from the action-inventory 140for carrying out the action indicated by the words 310. Uponidentification, the agent interface component 126 can render the userinterface component 142 as an overlay component 315 superimposed on topof the graphical user interface 305 of the foreground process 150. Inthe example depicted, the user interface component 142 rendered as theoverlay component 315 can include the words 310 of the requestcorresponding to the action, “How many steps?” In addition, the userinterface component 142 can also have the resultant output from carryingout the action, “You have taken 3147 steps today.” The user interfacecomponent 142 rendered as the overlay component 315 can also include acommand button 320. Upon interaction with the command button 320, theagent interface component 125 can close the overlay component 315,causing the user interface component 142 to disappear from the renderingon the display 148 of the client device 104.

FIG. 4 illustrates a block diagram of an example method 400 of rendingvisual components on applications. The method 400 can be implemented orexecuted by the system 100 described above in conjunction with FIGS. 1-3or system 500 detailed below in conjunction with FIG. 5. In briefoverview, the NLP component 116 can receive an input audio signal (405).The NLP component 116 can parse the input audio signal (410). The actionhandler component 120 can select an action-inventory 140 (415). Theaction handler component 120 can generate an address using theaction-inventory 140 (420). The action handler component 120 cangenerate an action data structure (425). The agent interface component126 can direct the action data structure (430). The agent interfacecomponent 126 can determine whether a user interface component 142 isauthorized to be presented with a foreground application (435). Ifdetermined to be authorized, the agent interface component 126 canpresent the user interface component 142 (440). If determined to be notauthorized, the agent interface component 126 can invoke an agentapplication 110 associated with the user interface component (445).

In further detail, the NLP component 116 can receive an input audiosignal (405). The NLP component 116 can receive one or more data packetsincluding the input audio signal acquired at a sensor (e.g., themicrophone 146) on the client device 104. For example, the NLP component116 of the digital assistant application 108 executed at least partiallyby the data processing system 102 can receive the input audio signal.The input audio signal can include a conversation facilitated by thedigital assistant application 108. The conversation can include one ormore inputs and outputs. The conversation can be audio based, textbased, or a combination of audio and text. The input audio signal caninclude text input, or other types of input that can provideconversational information. When the input audio signal is received, theclient device 104 can have applications running as the foregroundprocess 150 and the non-foreground process 152.

The NLP component 116 can parse the input audio signal (410). By parsingthe input audio signal, the NLP component 116 can identify a request andone or more parameters using various natural language processingtechniques. The request can be an intent or request that can befulfilled by the digital assistant application 108 or the agentapplication 110. The parameters can define the request. Based on therequest, the NLP component 116 can determine that the requestcorresponds to one of the functions of the agent application 110.

The action handler component 120 can select an action-inventory 140(415). Based on the request identified from the input audio signal, theaction handler component 120 can select the action-inventory 140 fromthe set maintained on the data repository 128. For each action-inventory140, the action handler component 120 can compare the request with therequest identifier of the action-inventory 140. The comparison can beperformed using a semantic knowledge graph. From the comparison, theaction handler component 120 can determine that the request matches therequest identifier of the action-inventory 140. In response to thedetermination, the action handler component 120 can select theaction-inventory 140 from the set maintained on the data repository 128.The selected action-inventory can indicate that the user interfacecomponent 142 of the agent application 110 that is not running as theforeground process 150 is to be presented.

The action handler component 120 can generate an address using theaction-inventory 140 (420). The generation of the address can be inaccordance with an address template of the action-inventory 140. Theaddress template can have a first portion and a second portion. Thefirst portion can reference the agent application 110 or the agentservice 106 for the agent application 110 to carry out the action. Thesecond portion can reference the action and can include one or moreinput variables for the action. The action handler component 120 cantake the first portion and the second portion from the address templatein generating the address. The action handler component 120 can insertor populate the parameters into the input variables of the secondportion of the address template.

The action handler component 120 can generate an action data structure(425). The action data structure can include a header and a body. Theaction handler component 120 can insert the address generated inaccordance with the address template of the action-inventory 140 intothe header of the action data structure. The action handler component120 can set the address as a destination address of the header to routethe action data structure to the agent application 110 or the agentservice 106 for the agent application 110.

The agent interface component 126 can direct the action data structure(430). The agent interface component 126 can direct the action datastructure to the agent application 110. The agent interface component126 can invoke the agent application 110 using the action data structureand can pass the action data structure to the agent application 110. Theagent application 110 in turn can parse the action data structure toidentify the action and one or more parameters form the address includedin the action data structure. The agent application 110 can execute theaction in accordance with the parameters.

The agent interface component 126 can determine whether a user interfacecomponent 142 is authorized to be presented with a foregroundapplication (435). The determination of whether the user interfacecomponent 142 is authorized can be in accordance with an authorizationpolicy. The authorization policy can specify whether the output of theagent application 110 is permitted or restricted from concurrentpresentation with the graphical user interface of the applicationrunning as the foreground process 150. The agent interface component 126can identify the application running in the foreground process 150. Theagent interface component 126 can compare the application with thespecifications of the authorization policy. When the authorizationpolicy permits concurrent presentation, the agent interface component126 can determine that the user interface component 142 is authorized tobe presented. Otherwise, when the authorization policy restricts theconcurrent presentation, the agent interface component 126 can determinethat the user interface component 142 is not authorized to be presentedwith the application running as the foreground process 150.

If determined to be authorized, the agent interface component 126 canpresent the user interface component 142 (440). The agent interfacecomponent 126 can identify the user interface component 142 from theselected action-inventory 140 (e.g., using an address include therein).The agent interface component 126 can render the identified userinterface component 142 as an overlay on the graphical user interface ofthe application running in the foreground process 150. The agentinterface component 126 can include the request for the action and theoutput generated by the agent application 110 in the user interfacecomponent 142.

On the other hand, if determined to be not authorized, the agentinterface component 126 can invoke an agent application 110 associatedwith the user interface component 142 (445). The agent interfacecomponent 126 can remove the original application running from theforeground process 150 and set the application to the non-foregroundprocess 152, thereby removing the rendering of the graphical userinterface of the application. The agent interface component 126 can setwith the agent application 110 as the foreground process 150. The agentinterface component 126 can also render the graphical user interface ofthe agent application 110 on the display 148 of the client device.

FIG. 5 is a block diagram of an example computer system 500. Thecomputer system or computing device 500 can include or be used toimplement the system 100 or its components such as the data processingsystem 102. The computing system 500 includes a bus 505 or othercommunication component for communicating information and a processor510 or processing circuit coupled to the bus 505 for processinginformation. The computing system 500 can also include one or moreprocessors 510 or processing circuits coupled to the bus for processinginformation. The computing system 500 also includes main memory 515,such as a random access memory (RAM) or other dynamic storage device,coupled to the bus 505 for storing information and instructions to beexecuted by the processor 510. The main memory 515 can be or include thedata repository 128. The main memory 515 can also be used for storingposition information, temporary variables, or other intermediateinformation during execution of instructions by the processor 510. Thecomputing system 500 may further include a read-only memory (ROM) 520 orother static storage device coupled to the bus 505 for storing staticinformation and instructions for the processor 510. A storage device525, such as a solid state device, magnetic disk or optical disk, can becoupled to the bus 505 to persistently store information andinstructions. The storage device 525 can include or be part of the datarepositories 128.

The computing system 500 may be coupled via the bus 505 to a display535, such as a liquid crystal display or active matrix display, fordisplaying information to a user. An input device 530, such as akeyboard including alphanumeric and other keys, may be coupled to thebus 505 for communicating information and command selections to theprocessor 510. The input device 530 can include a touch screen display535. The input device 530 can also include a cursor control, such as amouse, a trackball, or cursor direction keys, for communicatingdirection information and command selections to the processor 510 andfor controlling cursor movement on the display 535. The display 535 canbe part of the data processing system 102, the client devices 104, orother components of FIG. 1, for example.

The processes, systems and methods described herein can be implementedby the computing system 500 in response to the processor 510 executingan arrangement of instructions contained in main memory 515. Suchinstructions can be read into main memory 515 from anothercomputer-readable medium, such as the storage device 525. Execution ofthe arrangement of instructions contained in main memory 515 causes thecomputing system 500 to perform the illustrative processes describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the instructions contained in main memory515. Hard-wired circuitry can be used in place of or in combination withsoftware instructions together with the systems and methods describedherein. Systems and methods described herein are not limited to anyspecific combination of hardware circuitry and software.

Although an example computing system has been described in FIG. 5, thesubject matter including the operations described in this specificationcan be implemented in other types of digital electronic circuitry or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them.

For situations in which the systems discussed herein collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity to control whether programs orfeatures that may collect personal information (e.g., information abouta user's social network, social actions, or activities; a user'spreferences; or a user's location), or to control whether or how toreceive content from a content server or other data processing systemthat may be more relevant to the user. In addition, certain data may beanonymized in one or more ways before it is stored or used, so thatpersonally identifiable information is removed when generatingparameters. For example, a user's identity may be anonymized so that nopersonally identifiable information can be determined for the user, or auser's geographic location may be generalized where location informationis obtained (such as to a city, postal code, or state level), so that aparticular location of a user cannot be determined. Thus, the user mayhave control over how information is collected about him or her and usedby the content server.

The subject matter and the operations described in this specificationcan be implemented in digital electronic circuitry or in computersoftware, firmware, or hardware, including the structures disclosed inthis specification and their structural equivalents, or in combinationsof one or more of them. The subject matter described in thisspecification can be implemented as one or more computer programs, e.g.,one or more circuits of computer program instructions, encoded on one ormore computer storage media for execution by, or to control theoperation of, data processing apparatuses. Alternatively or in addition,the program instructions can be encoded on an artificially generatedpropagated signal, e.g., a machine-generated electrical, optical, orelectromagnetic signal that is generated to encode information fortransmission to suitable receiver apparatus for execution by a dataprocessing apparatus. A computer storage medium can be, or be includedin, a computer-readable storage device, a computer-readable storagesubstrate, a random or serial-access memory array or device, or acombination of one or more of them. While a computer storage medium isnot a propagated signal, a computer storage medium can be a source ordestination of computer program instructions encoded in an artificiallygenerated propagated signal. The computer storage medium can also be, orbe included in, one or more separate components or media (e.g., multipleCDs, disks, or other storage devices). The operations described in thisspecification can be implemented as operations performed by a dataprocessing apparatus on data stored on one or more computer-readablestorage devices or received from other sources.

The terms “data processing system,” “computing device,” “component,” or“data processing apparatus” encompass various apparatuses, devices, andmachines for processing data, including, by way of example, aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations of the foregoing. The apparatus can includespecial-purpose logic circuitry, e.g., an FPGA (field-programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures. The components of system100 can include or share one or more data processing apparatuses,systems, computing devices, or processors.

A computer program (also known as a program, software, softwareapplication, app, script, or code) can be written in any form ofprogramming language, including compiled or interpreted languages,declarative or procedural languages, and can be deployed in any form,including as a stand-alone program or as a module, component,subroutine, object, or other unit suitable for use in a computingenvironment. A computer program can correspond to a file in a filesystem. A computer program can be stored in a portion of a file thatholds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs (e.g., components of the data processing system 102)to perform actions by operating on input data and generating output. Theprocesses and logic flows can also be performed by, and apparatuses canalso be implemented as, special purpose logic circuitry, e.g., an FPGA(field-programmable gate array) or an ASIC (application-specificintegrated circuit). Devices suitable for storing computer programinstructions and data include all forms of non-volatile memory, mediaand memory devices, including by way of example semiconductor memorydevices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks,e.g., internal hard disks or removable disks; magneto optical disks; andCD-ROM and DVD-ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

The subject matter described herein can be implemented in a computingsystem that includes a back end component, e.g., as a data server, orthat includes a middleware component, e.g., an application server, orthat includes a front end component, e.g., a client computer having agraphical user interface or a web browser through which a user caninteract with an implementation of the subject matter described in thisspecification, or a combination of one or more such back end,middleware, or front end components. The components of the system can beinterconnected by any form or medium of digital data communication,e.g., a communication network. Examples of communication networksinclude a local area network (“LAN”) and a wide area network (“WAN”), aninter-network (e.g., the Internet), and peer-to-peer networks (e.g., adhoc peer-to-peer networks).

The computing system such as system 100 or system 500 can includeclients and servers. A client and server are generally remote from eachother and typically interact through a communication network (e.g., thenetwork 114). The relationship of client and server arises by virtue ofcomputer programs running on the respective computers and having aclient-server relationship to each other. In some implementations, aserver transmits data (e.g., data packets representing a content item)to a client device (e.g., for purposes of displaying data to andreceiving user input from a user interacting with the client device).Data generated at the client device (e.g., a result of the userinteraction) can be received from the client device at the server (e.g.,received by the data processing system 102 from the client devices 104or the agent service 106).

While operations are depicted in the drawings in a particular order,such operations are not required to be performed in the particular ordershown or in sequential order, and all illustrated operations are notrequired to be performed. Actions described herein can be performed in adifferent order.

The separation of various system components does not require separationin all implementations, and the described program components can beincluded in a single hardware or software product. For example, the NLPcomponent 116, the audio signal generator component 118, the actionhandler component 120, the response selector component 122, the agentregistry component 124, and the agent interface component 126 can be asingle component, app, or program, or a logic device having one or moreprocessing circuits, or part of one or more servers of the dataprocessing system 102.

Having now described some illustrative implementations, it is apparentthat the foregoing is illustrative and not limiting, having beenpresented by way of example. In particular, although many of theexamples presented herein involve specific combinations of method actsor system elements, those acts and those elements may be combined inother ways to accomplish the same objectives. Acts, elements, andfeatures discussed in connection with one implementation are notintended to be excluded from a similar role in other implementations.

The phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including,” “comprising,” “having,” “containing,” “involving,”“characterized by,” “characterized in that,” and variations thereofherein, is meant to encompass the items listed thereafter, equivalentsthereof, and additional items, as well as alternate implementationsconsisting of the items listed thereafter exclusively. In oneimplementation, the systems and methods described herein consist of one,each combination of more than one, or all of the described elements,acts, or components.

Any references to implementations, elements, or acts of the systems andmethods herein referred to in the singular may also embraceimplementations including a plurality of these elements, and anyreferences in plural to any implementation, element, or act herein mayalso embrace implementations including only a single element. Referencesin the singular or plural form are not intended to limit the presentlydisclosed systems or methods, their components, acts, or elements tosingle or plural configurations. References to any act or element beingbased on any information, act, or element may include implementationswhere the act or element is based at least in part on any information,act, or element.

Any implementation disclosed herein may be combined with any otherimplementation or embodiment, and references to “an implementation,”“some implementations,” “one implementation,” or the like are notnecessarily mutually exclusive and are intended to indicate that aparticular feature, structure, or characteristic described in connectionwith the implementation may be included in at least one implementationor embodiment. Such terms as used herein are not necessarily allreferring to the same implementation. Any implementation may be combinedwith any other implementation, inclusively or exclusively, in any mannerconsistent with the aspects and implementations disclosed herein.

References to “or” may be construed as inclusive so that any termsdescribed using “or” may indicate any of a single, more than one, andall of the described terms. A reference to “at least one of ‘A’ and ‘B’”can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Suchreferences used in conjunction with “comprising” or other openterminology can include additional items.

Where technical features in the drawings, detailed description, or anyclaim are followed by reference signs, the reference signs have beenincluded to increase the intelligibility of the drawings, detaileddescription, and claims. Accordingly, neither the reference signs northeir absence have any limiting effect on the scope of any claimelements.

The systems and methods described herein may be embodied in otherspecific forms without departing from the characteristics thereof. Theforegoing implementations are illustrative rather than limiting of thedescribed systems and methods. Scope of the systems and methodsdescribed herein is thus indicated by the appended claims, rather thanthe foregoing description, and changes that come within the meaning andrange of equivalency of the claims are embraced therein.

What is claimed:
 1. A system to render visual components onapplications, comprising: a natural language processor executed on adata processing system having one or more processors, the naturallanguage processor to: receive a data packet comprising an input audiosignal detected by a sensor of a client device, the client devicedisplaying a graphical user interface of a first application in aforeground process on the client device; and parse the input audiosignal of the data packet to identify a request; an action handlerexecuted on the data processing system to: select an action-inventorythat executes an action corresponding to the request by a secondapplication, the second application installed on the client device andnot in the foreground process; and generate an action data structure inaccordance with the action-inventory; and an agent interface executed onthe data processing system to: provide the action data structure to thesecond application to cause the second application to parse the actiondata structure and execute the action to generate an output; determinethat the output of the second application from execution of the actionis authorized to be presented with the graphical user interface of thefirst application based on an authorization policy of the secondapplication; identify the user interface component of the secondapplication for the action-inventory, responsive to the determinationthe output of the second application is authorized to be presented withthe first application; and display, on the client device, the userinterface component including the output from the second applicationwith the graphical user interface of the first application authorized tobe presented with the second application.
 2. The system of claim 1,comprising: the action-inventory having an agent identifiercorresponding to the second application and a request identifiercorresponding to the action; the natural language processor to parse theinput audio signal of the data packet to identify an agent identifiercorresponding to an agent, the agent corresponding to the secondapplication installed on the client device; and the action handler toselect the action-inventory for executing the action having the agentidentifier corresponding to the agent identifier identified from parsingthe input audio signal.
 3. The system of claim 1, comprising the actionhandler to: determine that the interface mode indicator of theaction-inventory specifies rendering of the user interface component inexecuting the action; and identify the user interface component of thesecond application for the action-inventory, responsive to thedetermination that the interface mode indicator specifies rendering ofthe user interface component.
 4. The system of claim 1, comprising theagent interface to: determine that the client device is notauthenticated with the second application for the action-inventory tocarry out the action corresponding to a second request; and present,responsive to the determination that the client device is notauthenticated with the second application, a prompt interface on theclient device to authenticate the client device with the secondapplication to execute the action corresponding to the second request.5. The system of claim 1, comprising the agent interface to provide theaction data structure to the second application to cause the secondapplication to: monitor for an interaction event on the user interfacecomponent from the second application presented with the graphical userinterface of the first application; and process, responsive to detectionof the interaction event, the interaction event to update the userinterface component.
 6. The system of claim 1, comprising: the naturallanguage processor to receive the data packet via a digital assistantapplication, the data packet comprising the input audio signal detectedby the sensor of the client device, the client device displaying thegraphical user interface of the digital assistant applicationcorresponding to the first application in the foreground process; andthe agent interface to display, within the graphical user interface ofthe digital assistant application, the user interface componentincluding a subcomponent indicating the request identified from parsingthe input audio signal and the user interface component including theoutput from an agent corresponding to the second application.
 7. Thesystem of claim 1, comprising: the natural language processor to receivethe data packet, the data packet comprising the input audio signaldetected by the sensor of the client device, the client devicedisplaying the graphical user interface of a first agent correspondingto the first application in the foreground process; and the agentinterface to display the user interface component including the outputfrom the second application as an overlay on the graphical userinterface of the first agent.
 8. The system of claim 1, comprising theaction handler to provide the action data structure to the secondapplication to cause the second application to: parse the action datastructure to identify the action to be executed; generate the output byexecuting the action identified from the action data structure; andprovide the output for the user interface component to be presented withthe graphical user interface of the first application authorized to bepresented with the second application.
 9. The system of claim 1, whereinthe action data structure comprises an address to execute the action ofthe action-inventory.
 10. The system of claim 9, wherein the addresscomprises a first substring corresponding to the second application. 11.The system of claim 10, wherein the address comprises a second substringcorresponding to the action.
 12. The system of claim 11, wherein thesecond substring comprises at least one input variable used to executethe action.
 13. A method of rendering visual components on applications,comprising: receiving, by a data processing system having one or moreprocessors, a data packet comprising an input audio signal detected by asensor of a client device, the client device displaying a graphical userinterface of a first application in a foreground process on the clientdevice; parsing, by the data processing system, the input audio signalof the data packet to identify a request; selecting, by the dataprocessing system an action-inventory that executes an actioncorresponding to the request by a second application, the secondapplication installed on the client device and not the foregroundprocess; generating, by the data processing system, an action datastructure in accordance with the action-inventory; providing, by thedata processing system, the action data structure to the secondapplication to cause the second application to parse the action datastructure and execute the action to generate an output; determining, bythe data processing system, that the output of the second applicationfrom execution of the action is authorized to be presented with thegraphical user interface of the first application based on anauthorization policy of the second application; identifying, by the dataprocessing system, the user interface component of the secondapplication for the action-inventory, responsive to the determinationthe output of the second application is authorized to be presented withthe first application; and displaying, by the data processing system, onthe client device, the user interface component including the outputfrom the second application with the graphical user interface of thefirst application authorized to be presented with the secondapplication.
 14. The method of claim 13, comprising: determining, by thedata processing system, that the client device is not authenticated withthe second application for the action-inventory to carry out the actioncorresponding to a second request; and presenting, by the dataprocessing system, responsive to the determination that the clientdevice is not authenticated with the second application, a promptinterface on the client device to authenticate the client device withthe second application to execute the action corresponding to the secondrequest.
 15. The method of claim 13, comprising: receiving, by the dataprocessing system, the data packet via a digital assistant application,the data packet comprising the input audio signal detected by the sensorof the client device, the client device displaying the graphical userinterface of the digital assistant application corresponding to thefirst application in the foreground process; and displaying, by the dataprocessing system, within the graphical user interface of the digitalassistant application, the user interface component including asubcomponent indicating the request identified from parsing the inputaudio signal and the user interface component including the output froman agent corresponding to the second application.
 16. The method ofclaim 13, comprising providing, by the data processing system, theaction data structure to the second application to cause the secondapplication to: monitor for an interaction event on the user interfacecomponent from the second application presented with the graphical userinterface of the first application; and process, responsive to detectionof the interaction event, the interaction event to update the userinterface component.
 17. The method of claim 13, wherein the action datastructure comprises an address to execute the action of theaction-inventory.
 18. The method of claim 17, wherein the addresscomprises a first substring corresponding to the second application. 19.The method of claim 18, wherein the address comprises a second substringcorresponding to the action.
 20. The method of claim 19, wherein thesecond substring comprises at least one input variable used to executethe action.